Problem moving catalog for elements 15 on Windows 10

[Guest]

I'm trying to move a catalog db and CameraRaw db from a win xp/Elements 7 installation to Win 10/Elements 15. The catalog gets moved, but RAW files from only one camera are not present.  All other camera RAW files move and all non raw, mainly jpeg, also move.  The CameraRaw db works with the RAW files that transferred and if I manually reimport the RAW files that didn't make the xfer.  However, manually importing the missing RAW files is not a good option, because all the version sets and import batch matching v the edited/manipulated versions stays broken. Has anyone dealt with this kind of problem?

[MichelBParis]

I don't understand what you are trying to do by 'moving' catalog.db files: the catalogs are folders. They include databases like catalog.pse15.db and many other files and subfolder. You have to convert the catalogs (the whole folders) to the new format by using the relevant button in the catalog manager. That creates a copy of the catalog in the new format.

[Guest]

I did not move just the .pse7db file, I moved the whole database (Whole catalog folder).

[MichelBParis]

ps45422046  wrote

I did not move just the .pse7db file, I moved the whole database (Whole catalog folder).

Yes, you can move the whole catalog folder and it will be available to pse7, but you have to convert it for pse15 from the catalog manager.

[Guest]

It was converted, and the whole catalog was moved and it still has the problems mentioned.  I wouldn't have asked the question if it was a straight forward problem.

[MichelBParis]

ps45422046  wrote

It was converted, and the whole catalog was moved and it still has the problems mentioned. 

Nobody can understand that from your initial post, forgive me if I asked, but at least, that part of your problem is clear now.

I wouldn't have asked the question if it was a straight forward problem.

Yes, I believe you, but I still don't understand a part of your question: do you mean you are using the Camera Raw database instead of the usual xmp sidecar files for raw files?

Also:

All other camera RAW files move and all non raw, mainly jpeg, also move.

So, you are not only moving the catalogs, you are also moving the library (the media files tre). Some details will be useful because if you don't use the backup/restore process, you get disconnected files.

Move Elements Organizer catalog | Elements 6 or later

I have never had problems like yours in the many conversions and transfers I did on all Elements versions, but I have always used the xmp sidecars solution, not the CameraRaw db (except for a few tests and without conversions).

[Guest]

The CameraRaw db is not the problem (I'm not using xmp sidecars). It works for all files including those that get manually reimported.

• The Catalog (folder) was physically transferred to a new system xp -> win10 and converted/optimized.
• The CameraRaw was also similarly transferred.
• The media files were also physically moved to a NAS.
• All files are initially disconnected after conversion as is to be expected, but the folder structure was retained, so after pointing the reconnection process to the new location all files get reconnected except the RAW files from the single camera.
• But those missing RAW files do not even show up in the initial list of disconnected files.
• The missing RAW files are interspersed in the same folders as other camera's RAW files that are found.
• All the missing RAW files belong to a DMC-FZ30.
• A new piece of information is that the Version Sets that RAW files are in from ANY camera are missing.  (i.e. RAW -> JPEG set is nonexistent but RAW->JPEG1/JPEG2 set will still exist except it is missing the original RAW)
• There are over 51,000 media files in 1294 folders @ 236GB total.  That's another reason it can't be a manual fix.

It was all done this way because the original xp system has motherboard issues and cannot sustain heavy loads without crashing.  Thus, I cannot complete a backup operation on the xp system.

[MichelBParis]

Thanks for the detailed description.

Unfortunately, I have no precise idea about the reason of the failure to get back those specific raw files. Generally the conversion process returns a message stating the files it could  not process. The reconnection process is not foolproof.

However, manually importing the missing RAW files is not a good option, because all the version sets and import batch matching v the edited/manipulated versions stays broken.

I am afraid that is the only way I can see. Since the files are physically on your NAS, doing a global import would skip all files already in your catalog and import missing ones. Did you try to 'Import' such a raw file as a test?

If that works, you are losing the links for version sets as expected: then the only way to group back originals and versions is to use the 'suggest stack' option in visual searches; not easy, I know.