dcm4chee-2.15.0 - "No Presentation Context for Abstract Syntax" when sending images from PRISMA Siemens scanner

[Vittorio Iacovella]

Dear dcm4che experts,

I am experiencing problems in sending images from a Siemens Scanner (Prisma - 3T) equipped with Syngo VE11C to a dcm4chee 2.15.0 (mysql) PACS.

In our facility we previously had a 4T Scanner equipped with a previous version of SYNGO. 

We (happily) worked with that scanner and dcm4chee 2.15.0 for many years. dcm4chee 2.15.0 was, among the other things, part of a complex, in - house built system to retrieve data in a safe way.

I set up the connection between the new 3T scanner and dcm4chee-2.15.0 in a very easy way. SYNGO "verification" (basically a DICOM echo, I suppose) works fine and the two dicom nodes acknowledge each other successfully.

However, when I try to send images to the pacs, I receive the following error (from dcm4chee-2.15.0 log):

sending AAssociateAC
        appCtxName:     1.2.840.10008.3.1.1.1/DICOM Application Context Name
        implClass:      1.2.40.0.13.1.1
        implVersion:    dcm4che-1.4.28
        calledAET:      DCM4CHEE
        callingAET:     AN_MEDCOMNT204
        maxPDULen:      16352
        asyncOpsWindow:
        pc-1:   3 - abstract-syntax-not-supported
                ts=1.2.840.10008.1.2.1/Explicit VR Little Endian

replicated for - as far as I understood - as many times as the number of images I am trying to send.

I finally receive the following message:

closing connection - Socket[addr=/10.231.10.10,port=54307,localport=11112]
2018-04-18 15:24:43,785 ERROR -> (TCPServer-1) [ActiveAssociationImpl] org.dcm4che.net.PDUException: Received A-ABORT
        source=0 - service-user
        reason=0 - reason-not-specified

- I assume that connections and ports work fine here, as well as the connection between the nodes. DICOM echo works and the sending procedure, as you can see, starts;

- I verified from jmx-console on dcm4chee-2.15.0 that all the transfer syntax and compression methods are enabled;

To exclude other potential problems, I also performed a couple other checks:

-- I tried to send the images from the scanner to another PACS. Specifically, the latest dcm4chee PACS(dcm4chee-arc-light-5.13.0). Here the sending operation succeed, with no specific configuration tricks on both sides;

-- I tried, then, to export the study I received on the latest PACS to the old one from the web-interface. The sending fails, and I extracted from server log the following error, which sounds very similar to the other one:

org.dcm4che3.net.NoPresentationContextException: No Presentation Context for Abstract Syntax: 1.2.840.10008.5.1.4.1.1.7 - Secondary Capture Image Storage negotiated
        at deployment.dcm4chee-arc-ear-5.13.0-mysql.ear//org.dcm4chee.arc.store.scu.impl.RetrieveTaskImpl.store(RetrieveTaskImpl.java:153)
        at deployment.dcm4chee-arc-ear-5.13.0-mysql.ear//org.dcm4chee.arc.store.scu.impl.RetrieveTaskImpl.run(RetrieveTaskImpl.java:127)
        at deployment.dcm4chee-arc-ear-5.13.0-mysql.ear//org.dcm4chee.arc.export.dicom.DicomExporter.export(DicomExporter.java:105)
        at deployment.dcm4chee-arc-ear-5.13.0-mysql.ear.dcm4chee-arc-war-5.13.0-unsecure.war//org.dcm4chee.arc.export.rs.ExporterRS.export(ExporterRS.java:200)
        at deployment.dcm4chee-arc-ear-5.13.0-mysql.ear.dcm4chee-arc-war-5.13.0-unsecure.war//org.dcm4chee.arc.export.rs.ExporterRS.exportStudy(ExporterRS.java:127)
        at deployment.dcm4chee-arc-ear-5.13.0-mysql.ear.dcm4chee-arc-war-5.13.0-unsecure.war//org.dcm4chee.arc.export.rs.ExporterRS$Proxy$_$$_WeldClientProxy.exportStudy(Unknown Source)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.base/java.lang.reflect.Method.invoke(Unknown Source)

-- I also exported the images on a storage and from there I used dcm4che DICOM toolkit utility (v 5.13) storescu to send the images to dcm4chee-2.15.0 in the following way:

storescu -c DCM4CHEE@<dcm4chee-2.15.0-address>:11112 /path/to/my/IMA/files

this returns an error which sounds similar as before:

org.dcm4che3.net.NoPresentationContextException: No Presentation Context for Abstract Syntax: 1.2.840.10008.5.1.4.1.1.4 - MR Image Storage negotiated
        at org.dcm4che3.net.Association.pcFor(Association.java:847)
        at org.dcm4che3.net.Association.cstore(Association.java:881)
        at org.dcm4che3.net.Association.cstore(Association.java:875)
        at org.dcm4che3.tool.storescu.StoreSCU.send(StoreSCU.java:484)
        at org.dcm4che3.tool.storescu.StoreSCU.sendFiles(StoreSCU.java:388)
        at org.dcm4che3.tool.storescu.StoreSCU.main(StoreSCU.java:296)

Do you have any idea about this "No Presentation Context for Abstract Syntax:" / "abstract-syntax-not-supported" error? Any experience of compatibility problems between new SYNGO versions and dcm4chee-2.15.0 ?

Thank you in any case.

Best,

Vittorio

--

Vittorio Iacovella

IT Technical Support Staff

CIMeC - Center for Mind/Brain Sciences

The University of Trento

[Vittorio Iacovella]

Hello All,

I m still dealing with this error. In addition to the information I mentioned in the previous message, I would add that 

I checked the dicom conformance statements and the dicom header and I checked that the IDs for AcceptedTransferSyntaxForImageSOPClasses and AcceptedOtherSOPClasses were explicitly mentioned in dcm4chee-2.15.0 jmx console. They look exactly the same as the dicom files produced by the new Siemens scanner.

Unfortunately this did not bring any substantial change. I still get the same  "No Presentation Context for Abstract Syntax:" / "abstract-syntax-not-supported" error.

Any ideas or experiences of compatibility problems between new Siemens scanners and dcm4chee-2.15.0?

Thank you in any case.

Best,

Vittorio

--

Vittorio Iacovella

IT Technical Support Staff

CIMeC - Center for Mind/Brain Sciences

The University of Trento

[Denis Shpekin]

1.2.840.10008.5.1.4.1.1.7  standart SC

1.2.840.10008.5.1.4.1.1.4   standart MR

Accepts always

can not be checked without source files

[Vittorio Iacovella]

Dear Denis Shpekin,

thanks for your answer.

I could enclose a dicom file generated by the scanner in order to check potential problems in file sending.

As far as I understood, you are suggesting to include these two UID to service=StoreScp > AcceptedImageSOPClasses

am I understanding your suggestion correctly?

Thank you in any case.

Best,