Pictures, edits, ratings and albums aren't saved after closing C1

Simon

• June 19, 2023 09:10

Lately I've been experiencing problems with C1, which make the program unusable. After closing C1 no imports*, edits, ratings or user collections/albums are saved. *Imports are copied from the SD card on to the harddrive, however aren’t saved in the catalogue (I’m not using sessions). On closing or restarting C1 there’s no error message that the program closed unexpectedly. However all adjustments are gone. When verifying the catalogue, sometimes an error message will come up (unfortunately, I can’t reproduce it right now, since right now the verification goes through without a problem). Some previously created albums seem to be corrupted – I can see the amount of pictures that are supposed to be in it, however the pics don’t show up and C1 tells me, that there’re no images in the folder (the pictures haven’t been moved to a new location and they do show up in different albums). In the log file I can see a message that should relate to this:

UNIQUE constraint failed: ZVARIANTINCOLLECTION.ZCOLLECTION, ZVARIANTINCOLLECTION.ZVARIANT

RequestPopulateContents is called for '01'. (01 being the name of the album)

Cancelling collection filling of '2022' (2022 being the name of the project in which the album sits)

 

Backing up the catalogue will sometimes go through and sometimes show an error message: “The backup process of “Capture One” has failed. An error occurred during the backup process”

Other error messages in the log file include:

• “Exception while trying to add VariantInCollection links in PersistNewItemsTask : code = Constraint (19), message = System.Data.SQLite.SQLiteException (0x800027AF): constraint failed **| UNIQUE constraint failed: ZVARIANTINCOLLECTION.ZCOLLECTION, ZVARIANTINCOLLECTION.ZVARIANT”

• Error: Failed to GetCollectionVariantIds. If the connection is closed it is ok.

Environment:

• Monitor: LG 27ul850

• Camera: Sony A7iii and A7iv

• GPU: RTX 2060 Super 8GB

• CPU: AMD Ryzen 3900

• Others: 64gb of ram

Capture One version Migrated from (if applicable)

16.2.2, updated recently from a previous 16.x version, in which the issue also occurred. I updated to C1 23 from C1 22 some time last year.

 

Any help is appreciated!

1

• 

  ernst.w

  • July 20, 2023 11:19

  Mostly a catalog is or can be repaired during or after checking it. This - if I understand your writing - does not happen. One way would be to go back to last (functional) backup.

  There is another - I would say "last" - way to repair a catalog. It was a hint from C1 support ... and it worked in similiar cases:

  • Try to check you catalog as good as possibel. Then close it.
  • Create a new empty catalog.
  • Import your best version of you catalog into this new one.
  • During import there are a lot of checks. you will be ask e.g. for (offline) images without guilty path and so on.
  • (I personally have leared to stop the import, when I see a lot of similiar errors and correct them before starting a complete new attempt. But you can correct every singe error one by one too.)
  • It lasts as long as needed. Be patient!
  • When import is finished, you will find an album wherein you find your projects, groups and album structure. You can pull the content out of the temporar collection (and delete the now empty one).

  I needed this way twice in 15 years. In my cases it worked nearly perfect. (of course demaged imaged may fail.)

  Kind regards
  Ernst

  0

Please sign in to leave a comment.