Failed SOP Instances

How to backup and/or replicate your PacsOne Server database for redunancy and fault tolerance?
Post Reply
rsmith
Posts:1
Joined:Tue Mar 22, 2016 3:55 pm
Failed SOP Instances

Post by rsmith » Tue Mar 22, 2016 4:14 pm

Hello Pacsone,

When we autoroute/manual forward a session (CT/MR/US) to a Mirth Connect we get failed Jobs "all the time" with the following error. Please note only 1 dicom file out of so many in a study gets to Mirth connect rest fails.

Failed SOP Instances:
1.2.840.113680.1.103.56736.1458586439.114302.1.1
1.2.840.113680.1.103.56736.1458586439.114302.1.2
1.2.840.113680.1.103.56736.1458586439.114302.1.3
...

We have reduced Maximum Number of Simultaneous Outbound Connections to 1 but still no effect.
If we have single US dicom file with multi-frame or an Xray that works without any issue. Problems occurs only when single study has multiple files.

Mirth connect has been setup as DICOM Listner which simply copies dicom files to a directory for backup purposes.

Regards,
Ric

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Re: Failed SOP Instances

Post by pacsone » Wed Mar 23, 2016 2:47 pm

Did you check the PacsOne Server log file under the "log/${AeTitle}/" sub-folder where PacsOne is installed, and see if PacsOne had logged any error that correspond to the transfer of this study?

Post Reply