Orthanc::OrthancException

Google Groups archive
1

Dear Orthanc User Group,

I recently had one of my pac servers stop running and gave me the error message:
"terminate called after throwing an instance of 'Orthanc::OrthancException'"

I was not able to find the meaning of the error in a google search, but I
recognized that disconnecting the SQLite database fixed the problem. I was able
to store files and read files in the new database with the old settings of the
configuration file without a problem.

I am running Centos 7.9 and have a complied version of orthanc 1.5.6 and have
been operational without any problems since around 2018. The only thing that
was recently different is we created a vpn between offices.

Here are my questions :

#1. What does Orthanc::Orthanc::Exception mean as to a fatal error, and is there
a way to fix it.

#2. Is there a way to transfer the dicom files to teh new database if there is
no way to fix the problem.

Thank you!!

2

Hi Gregory,

Unfortunately, Orthanc::Orthanc::Exception is a very generic error that does not give any hint. We are constantly trying to improve error reporting but it looks like in 1.5.6, this one was not covered. You could safely try to run the latest version on this DB to have, hopefully, improved error reporting.

I’m not sure to understand what you mean by “disconnecting the SQLite DB”.

However, if you start from a brand new empty DB, you’ll have to re-ingest all files into Orthanc again. In this case, you would need to define a new StorageDirectory for the new Orthanc and re-import all files from the StorageDirectory from the previous Orthanc. There are python scripts for that: https://hg.orthanc-server.com/orthanc/file/tip/OrthancServer/Resources/Samples/ImportDicomFiles/ImportDicomFiles.py

HTH,

Alain