Orthanc 1.5.6: Failed DICOM Store SCP

Google Groups archive
1

Hi, friends!

I’d like to ask help in identifying the root cause of this problem. We’re attempting to send a couple of images from a DICOM client to Orthanc 1.5.6. It seems the first sending fails with the message below:

W0405 21:03:45.425937 main.cpp:712] Orthanc has started
W: DcmItem: Invalid Element (0002,0000) found in data set
W: DcmItem: Invalid Element (0002,0001) found in data set
W: DcmItem: Invalid Element (0002,0002) found in data set
W: DcmItem: Invalid Element (0002,0003) found in data set
W: DcmItem: Invalid Element (0002,0010) found in data set
W: DcmItem: Invalid Element (0002,0012) found in data set
W: DcmItem: Invalid Element (0002,0013) found in data set
W: DcmItem: Invalid Element (0002,0016) found in data set
W: DIMSE Warning: (RECEPCAO,UNIDADE-342): DIMSE receiveDataSetInMemory: dset->read() Failed (Illegal call, perhaps wrong parameters)
E0405 21:04:24.311561 StoreScp.cpp:304] Store SCP Failed: DIMSE Failed to receive message
W: DcmItem: Element (0000,0000) found twice in one data set or item, ignoring second entry

(… several repetitions of the line above …)
W: DcmItem: Element (0000,0000) found twice in one data set or item, ignoring second entry
W: DcmItem: Length of element (ef3f,8936) is odd

I suppose the client is misbehaving when trying to send the image as the bold line shows. Alas, I don’t know much about the actual DICOM protocol binary communication when it comes to Store SCP.

Any help is greatly appreciated.

Best regards,

2

Hello Luiz,

Firstly, are you sure that your DICOM file is valid? This can be checked e.g. with the “dciodvfy” tool:
https://www.dclunie.com/dicom3tools.html

https://www.dclunie.com/dicom3tools/dciodvfy.html

Secondly, is your DICOM client a free and open-source software?

Indeed, we can’t provide support for proprietary software. Please get in touch with the commercial support of your viewer: You pay them to that purpose. As Orthanc is free and open-source software, they will be either able to reproduce and fix your issue, or to provide a way to reproduce the issue independently of their software so that you can fill a bug report in Orthanc.

If your client is free and open-source, just name it and provide sample DICOM data so that the Orthanc community can work on a fix by itself. The ideal for us is to be able to reproduce the issue using “storescu” from DCMTK, “gdcmscu” from GDCM, or “storescu” from dcm4che.

Regards,
Sébastien-