I recently ugraded to PSE 2022, and converted my catalogs. When I try to delete a file in the new catalog in PSE 2022, I get this error:
I have tried to do a repair, but the repair button is missing on the Catalog Manager:
I have tried the conversion several times, each time I get the same message.
I am using an Intel based iMac.
 
{Title edited by Moderator}
13
Replies
The Repair function has not been available on Mac since PSE 18. Why was this useful tool removed?
By @barrys51571289
I am on Windows since the start of the organizer, so I have used the 'repair' option hundred times as it is a general and recommended 'good practice' when using database engines. I have had many issues with catalogs but I have NEVER seen the 'repair' button repair anything. Even with power failures, the sqlite database engine is pretty good to prevent serious damage, so I would not bother at all if the button disappeared also in Windows.
Your question has very little chance to get an answer from Adobe, so here are my guesses.
Adobe tries hard to keep the same features and behaviors in Mac and Windows, but there remains a few differences. Another one for instance is the ability to store your catalog folder on a network drive.
In most cases I see them as the result of more safety constraints from Apple side to protect their users. Adobe does not choose to stop a feature, but they can no longer program them in new OS versions.
So how is the 'repair' function supposed to work? If you compare the catalog structures of the Organizer since the start, you have a Microsoft Access engine up to version 5. The catalog is not a folder, it's a single file, catalog.psa. The Sqlite versio introduced with PSE6 makes the organizer available to Elements for Mac instead of Bridge. The catalog is now a folder with a bit more components than the main database. Then new new features are introduced in the organizer and are managed with new components added in the catalog folder.
Any serious database engine must have a builtin safety system to repair the database in case of a power failure or similar. My guess is that Adobe only programs an order to that Sqlite engine to do the repair. You can issue such an order yourself using an sqlite utility. However, what about other types of issues, corruption than the main database? Note that there are more sqlite databases in a catalog folder, including the thumbnail cache. Maybe the repair process from Adobe does repair more than the databases themselves, but I can't be sure.
So, my advice is to use the recent catalog backup function limited to the catalog folder. After each session, I allow that backup which is fast since it does not backup also the media files. I just had a situation last week where I recovered everything (I just had to wait for the thumbnail cache to be rebuilt in a night job).
I have now worked out that the combination of PSE 2022 and Macos 12.4 is corrupting the PSE catalogs. I started out with four working catalogs converted from PSE 2021. Over two days usage two of these have become corrupted. I have a total of 120,000 photographs stored, labelled, cataloged and tagged in PSE, built up over a fifteen year period. Restoring from backups doesn't help because the catalog just becomes corrupted again.
By @barrys51571289
Unfortunately, I can't help you for Mac specific issues. The only thing I can say is that in a conversion, the original is not changed in anyway except that it is renamed with a '1' suffix to allow the converted copy to keep the catalog name. So you can always convert again a catalog.
There are several posts about similar issues with the new OS versions of Macs, but similar does not mean it's your own particular problem. I would try to reach 'Customer Care' by chat or phone.
Thanks, I did, but all they did was send me a link which pointed me to the "Repair" function, which no longer exists on Mac, or suggest a restore. I did the restore and the newly restored catalog also got corrupted. I have been back and forward to Customer Care for a few weeks now, still haven't got an answer from them.
By @barrys51571289
I think that Adobe help staff who are reading this forum should take your issue more seriously.
We can't judge from this forum only if there is a precise bug or incompatibility; however if that were the case, there would be a flood of complaints pointing to the circumstances of the corruption.
In my experience, the catalog structure has become very complex and dependent on interractions with other software components and background tasks. So, I believe that now, you can't be sure of what a 'corruption' does mean. I have seen many cases where a catalog seemingly works ok but refuses to be backed up or converted. In your case, the previous catalogs may still work ok with the corresponding version but fail to be backed up or converted. If you could run the 'repair' function on your older OS version, you might get a significant message about if errors were found. Chances are that if no error were found, something else would still be wrong in your catalog. The implication would be that the 'corruption' did exist before the conversion process. Remember that the original catalog folder is never changed in the conversion, it is read, converted and written in a new folder.
So, my suggestion now is to try a troubleshooting step which is at the same time a possible middle solution. There is no official doc about it, but there is no risk to try it.
In my experience again, if you only keep the main sqlite database in the catalog folder, you can tell if the 'corruption' is in the main database (catalog.pseXXdb) or in the associated items in the catalog folder. So, create a new empty folder with only a copy of that original database. Try the conversion from this 'light' catalog. Same errors again? If not, double click on that file to start the organizer with that 'light' catalog. Either you get error messages or you get a useable catalog keeping all your keywords, albums, stacks and version sets, but losing face recognition and more.
Report back so that you may get more help especially from Adobe Staff and expert Mac users.
AdChoices