Skip to main content
patrickl27083915
Participant
January 28, 2022
Question

Failure to convert PSE 18 Catalog to PSE 2022

  • January 28, 2022
  • 2 replies
  • 484 views

Conversion failed wth the following error in 

 

'pse-conversion-log_My Catalog PSE 11.txt'

'An error was encountered in the sqlite database: UNIQUE constraint failed: db_change_timestamp_table.change_id
conversion log: Conversion Failed'

I tried opening the catalog file in DB Browser for SQLite. Looking at the db_change_timestamp_table, there are no duplicate change_ids, so I'm not sure why this error would be happening.


This topic has been closed for replies.

2 replies

Participant
December 2, 2022

Hi, I was getting the same error message. So I downloaded this SQLite browser https://sqlitebrowser.org

and edited a copy of my catalog file catlog.pse16db (you have to select (*all files) to see the file when opening it)

 

Once I opened my catalog file, I went to browse data and then selected the table db_change_timestamp_table.chang_id and then selected all the rows and deleted them, so the table was empty. I then saved my database file and was able to convert it in elements '22 with no errors. Just for the heck of it I also was able to have elements '18 successfully rebuild the index in my broken catalog db file. It only worked after I removed all the rows in db_change_timestamp_table.change_id.  I'm relieved I don't have to copy each individual caption and note from my previously broken old catalog to a new catalog in elements 22. Phew

Participant
December 2, 2022

*sorry I meant table db_change_timestamp_table. not ...table.change_id   

MichelBParis
Legend
January 28, 2022
quote

Conversion failed wth the following error in 

 

'pse-conversion-log_My Catalog PSE 11.txt'

'An error was encountered in the sqlite database: UNIQUE constraint failed: db_change_timestamp_table.change_id
conversion log: Conversion Failed'

I tried opening the catalog file in DB Browser for SQLite. Looking at the db_change_timestamp_table, there are no duplicate change_ids, so I'm not sure why this error would be happening.



By @patrickl27083915

Same error message here:

 

https://community.adobe.com/t5/photoshop-elements-discussions/fehler-bei-konvertierung-von-13-nach-2022/m-p/12691684#M77888

 

In that case, there was indeed a duplicate time stam in the database and the poster was able to remove it.

It might help if you could find the error jin the logs of the organizer as was reported by the other poster.

Also, a screenshot of the table like what I did would conferm the absence of duplicates.

 

 

patrickl27083915
Participant
February 1, 2022

Using the following statement

select *, count(*) duplicates
from db_change_timestamp_table
group by change_id
having duplicates > 1

There are no duplicate change_id records.

 

If you're talking about duplicate change_timestamp_table records with different change_ids, then yes those exist

select change_date_time, count(*) duplicates
from db_change_timestamp_table
group by change_date_time
having duplicates > 1

 

 

patrickl27083915
Participant
February 1, 2022

1) I have tried repairing and it says there is nothing to repair.
2) I tried putting the catalog db file in a new blank catalog folder, but this still gives the same unique change_id error