MOVESCU Unable to process

[metselar]

I have managed to retrieve all the Study UID's, Series UID's and SOP Instance UID's of all the images I want to retrieve via the findscu command.
The server is configured and knows my AETITLE with the correct corresponding port. However MOVESCU returns the following error:

C:\Users\wsservice\PycharmProjects\query>movescu -d -S -aet NUC1200326 -aec QR_XLNUC_SCP -aem NUC1200326 +P {my_ip:my_port} -k 0008,0052=SERIES -k 0020,000d=1.2.840.113619.2.290.3.514646400.121.1546239236.286 -k 0020,000e=1.3.6.1.4.1.25189.144027014141169248.20181231161207010 {SCP_IP} {SCP_PORT} -od {destination}

D: $dcmtk: movescu v3.6.5 2019-10-28 $
D:
D: Request Parameters:
D: ====================== BEGIN A-ASSOCIATE-RQ =====================
D: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.5
D: Our Implementation Version Name: OFFIS_DCMTK_365
D: Their Implementation Class UID:
D: Their Implementation Version Name:
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: PYNETDICOM
D: Called Application Name: QR_XLNUC_SCP
D: Responding Application Name: QR_XLNUC_SCP
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 0
D: Presentation Contexts:
D: Context ID: 1 (Proposed)
D: Abstract Syntax: =FINDStudyRootQueryRetrieveInformationModel
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
D: =LittleEndianExplicit
D: =BigEndianExplicit
D: =LittleEndianImplicit
D: Context ID: 3 (Proposed)
D: Abstract Syntax: =MOVEStudyRootQueryRetrieveInformationModel
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
D: =LittleEndianExplicit
D: =BigEndianExplicit
D: =LittleEndianImplicit
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-RQ ======================
I: Requesting Association
D: setting network send timeout to 60 seconds
D: setting network receive timeout to 60 seconds
D: Constructing Associate RQ PDU
D: PDU Type: Associate Accept, PDU Length: 203 + 6 bytes PDU header
D: 02 00 00 00 00 cb 00 01 00 00 51 52 5f 58 4c 4e
D: 55 43 5f 53 43 50 20 20 20 20 50 59 4e 45 54 44
D: 49 43 4f 4d 20 20 20 20 20 20 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 10 00 00 15 31 2e
D: 32 2e 38 34 30 2e 31 30 30 30 38 2e 33 2e 31 2e
D: 31 2e 31 21 00 00 19 01 00 00 00 40 00 00 11 31
D: 2e 32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32
D: 21 00 00 19 03 00 00 00 40 00 00 11 31 2e 32 2e
D: 38 34 30 2e 31 30 30 30 38 2e 31 2e 32 50 00 00
D: 30 51 00 00 04 00 00 70 00 52 00 00 13 31 2e 32
D: 2e 37 35 32 2e 32 34 2e 33 2e 33 2e 32 35 2e 37
D: 55 00 00 0d 57 49 51 52 53 43 50 5f 31 38 5f 32
D: 30
D: Parsing an A-ASSOCIATE PDU
D: Association Parameters Negotiated:
D: ====================== BEGIN A-ASSOCIATE-AC =====================
D: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.5
D: Our Implementation Version Name: OFFIS_DCMTK_365
D: Their Implementation Class UID: 1.2.752.24.3.3.25.7
D: Their Implementation Version Name: WIQRSCP_18_20
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: PYNETDICOM
D: Called Application Name: QR_XLNUC_SCP
D: Responding Application Name: QR_XLNUC_SCP
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 28672
D: Presentation Contexts:
D: Context ID: 1 (Accepted)
D: Abstract Syntax: =FINDStudyRootQueryRetrieveInformationModel
D: Proposed SCP/SCU Role: Default
D: Accepted SCP/SCU Role: Default
D: Accepted Transfer Syntax: =LittleEndianImplicit
D: Context ID: 3 (Accepted)
D: Abstract Syntax: =MOVEStudyRootQueryRetrieveInformationModel
D: Proposed SCP/SCU Role: Default
D: Accepted SCP/SCU Role: Default
D: Accepted Transfer Syntax: =LittleEndianImplicit
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-AC ======================
I: Association Accepted (Max Send PDV: 28660)
I: Sending Move Request
D: ===================== OUTGOING DIMSE MESSAGE ====================
D: Message Type : C-MOVE RQ
D: Presentation Context ID : 3
D: Message ID : 1
D: Affected SOP Class UID : MOVEStudyRootQueryRetrieveInformationModel
D: Data Set : present
D: Priority : medium
D: Move Destination : NUC1200326
D: ======================= END DIMSE MESSAGE =======================
I: Request Identifiers:
I:
I: # Dicom-Data-Set
I: # Used TransferSyntax: Little Endian Explicit
I: (0008,0052) CS [SERIES] # 6, 1 QueryRetriev
eLevel
I: (0020,000d) UI [1.2.840.113619.2.290.3.514646400.121.1546239236.286] # 52, 1
StudyInstanceUID
I: (0020,000e) UI [1.3.6.1.4.1.25189.144027014141169248.20181231161207010] # 54
, 1 SeriesInstanceUID
I:
D: DcmDataset::read() TransferSyntax="Little Endian Implicit"
W: Move response with error status (Failed: UnableToProcess)
I: Received Final Move Response
D: ===================== INCOMING DIMSE MESSAGE ====================
D: Message Type : C-MOVE RSP
D: Message ID Being Responded To : 1
D: Affected SOP Class UID : MOVEStudyRootQueryRetrieveInformationModel
D: Remaining Suboperations : 0
D: Completed Suboperations : 0
D: Failed Suboperations : 1
D: Warning Suboperations : 0
D: Data Set : none
D: DIMSE Status : 0xc001: Error: Failed - Unable to process
D: ======================= END DIMSE MESSAGE =======================
I: Releasing Association



Any Idea what the issue is here?

[Michael Onken]

Hi,

the PACS server can probably not connect back to you.

The +P option only requires to be the port, not the IP, to tell movescu which port it should listen for incoming images. The PACS server only uses the move AE title (provided with -aem) to lookup IP and port; what you provide with +P is not sent to the server at all. Therefore your AE Title has to be configured at the PACS server with IP and port so that the PACS server know how to connect to the desired (-aem) AE Title.

Also, make sure your client/receiving system is not behind a firewall.

Best regards,
Michael

[metselar]

Hello Michael,

Thanks for your reply! I have also tried to run in a separate command: storescp 4006 -od {my output directory}. My movescu command would then look like:

movescu -d -S -aet NUC1200326 -aec QR_XLNUC_SCP -aem NUC1200326 -k 0008,0052=SERIES -k 0020,000d=1.2.840.113619.2.290.3.514646400.121.1546239236.286 -k 0020,000e=1.3.6.1.4.1.25189.144027014141169248.20181231161207010 {SCP_IP} {SCP_PORT}

But unfortunately I get the same result. The PACS knows the title NUC1200326 and its IP:PORT settings. (set up to be port 4006). Also, I have checked with ICT and the port should not be behind a firewall...
Maybe I need to specify the transfersyntax? From the error message it looks like there is a difference between LittleEndianImplicit and LittleEndianExplicit?

regards,

Rutger

[Michael Onken]

Hi,

no you cannot influence the transfersytanx between PACS and image receiver, so you do not have to provide it via movescu.

If there is a problem between PACS server and image receiver on the connection, you should at least see a connection attempt in the storescp log.

I can't see a problem with the query just by looking at it, sorry....so firewall is my only guess.

Can you look into the server log? Can you retrieve from another PACS for testing?

Best,
Michael

[metselar]

Hello Michael,

I will try to get on the phone with some of the people that handle network systems in my hospital while I execute my command. Perhaps they can find out if there's blockage from a firewall.
However I am able to store c-find responses on this computer..

Regards,

Rutger