Hello Karsten, > Is there anything else I can provide to get this bug looked at ?
I am back from vacations. I will look at the upgrade problem as soon as possible. As a quick hack to unblock you, I would suggest to apply the "Generic replication" procedure [1]. In your case, the procedure would consist in the following steps: * Build from source the old versions of Orthanc and OrthancPostgreSQL that used to work against your database (respectively versions 0.8.x and 2.0 according to your first mail) * Uninstall and purge all the orthanc-related packages (make sure to backup your configuration files) * Remove the content of the "/etc/orthanc" folder * Reinstall the "orthanc" and "orthanc-postgresql" packages from scratch * Create a new database in PostgreSQL * Restore your configuration files * Edit "/etc/orthanc/postgresql.json" so that it points to the newly created database * Restart Orthanc: "sudo /etc/init.d/orthanc restart" * Run the old version of Orthanc with your old configuration files against your old database, making sure to change the DICOM/REST port so that it does not collide with the "4242/8042" default ports * Apply the "Generic replication" procedure [1] This upgrade problem should not occur again in the future, as I think that the database schema has reached its final state since Orthanc 1.0.0. Sorry for the inconvenience, Sébastien- [1] https://orthanc.chu.ulg.ac.be/book/users/replication.html#generic-replication
