movescu - Move Request Failed: 0006:0317

[cappa1983]

Hi All --

I'm trying to use movescu.exe to pull down studies, and for smaller studies, it works as expected, however, upon trying to pull down larger USMF, it processes the request for the first SOP UID, but then fails (tried several studies). I see that in the Debug output, there are two lines for the network send and receive that are set to 60 seconds, so I tried the

Code: Select all

-to

Code: Select all

-ta

and

Code: Select all

-td

options, but that didn't seem to help.

Any help is appreciated!

thanks!

Movescu Command:

Code: Select all

.\movescu.exe mainPACS 104 -P -xe -d -aet testAET -aec PACSAET -aem testAET -k 0008,0052=PATIENT -k 0010,0020="1752" +P 108 -od "c:\temp"

Here is the output:

Code: Select all

: $dcmtk: movescu v3.6.4 2018-11-29 $
D:
D: Request Parameters:
D: ====================== BEGIN A-ASSOCIATE-RQ =====================
D: Our Implementation Class UID:      1.2.276.0.7230010.3.0.3.6.4
D: Our Implementation Version Name:   OFFIS_DCMTK_364
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:    testAET 
D: Called Application Name:     PACSAET 
D: Responding Application Name: PACSAET 
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: =FINDPatientRootQueryRetrieveInformationModel
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: =MOVEPatientRootQueryRetrieveInformationModel
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: 201 + 6 bytes PDU header
D:   02  00  00  00  00  c9  00  01  00  00  48  4d  48  43  41  43
D:   50  53  53  20  20  20  20  20  20  20  48  59  50  45  52  49
D:   4f  4e  44  43  4d  32  31  39  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  1b  01  00  00  00  40  00  00  13  31
D:   2e  32  2e  38  34  30  2e  31  30  30  30  38  2e  31  2e  32
D:   2e  31  21  00  00  1b  03  00  00  00  40  00  00  13  31  2e
D:   32  2e  38  34  30  2e  31  30  30  30  38  2e  31  2e  32  2e
D:   31  50  00  00  2a  51  00  00  04  00  00  40  00  52  00  00
D:   0f  31  2e  32  2e  34  30  2e  30  2e  31  33  2e  31  2e  31
D:   55  00  00  0b  64  63  6d  34  63  68  65  2d  32  2e  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.4
D: Our Implementation Version Name:   OFFIS_DCMTK_364
D: Their Implementation Class UID:    1.2.40.0.13.1.1
D: Their Implementation Version Name: dcm4che-2.0
D: Application Context Name:    1.2.840.10008.3.1.1.1
D: Calling Application Name:    testAET 
D: Called Application Name:     PACSAET 
D: Responding Application Name: PACSAET 
D: Our Max PDU Receive Size:    16384
D: Their Max PDU Receive Size:  16384
D: Presentation Contexts:
D:   Context ID:        1 (Accepted)
D:     Abstract Syntax: =FINDPatientRootQueryRetrieveInformationModel
D:     Proposed SCP/SCU Role: Default
D:     Accepted SCP/SCU Role: Default
D:     Accepted Transfer Syntax: =LittleEndianExplicit
D:   Context ID:        3 (Accepted)
D:     Abstract Syntax: =MOVEPatientRootQueryRetrieveInformationModel
D:     Proposed SCP/SCU Role: Default
D:     Accepted SCP/SCU Role: Default
D:     Accepted Transfer Syntax: =LittleEndianExplicit
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: 16372)
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        : MOVEPatientRootQueryRetrieveInformationModel
D: Data Set                      : present
D: Priority                      : medium
D: Move Destination              : testAET 
D: ======================= END DIMSE MESSAGE =======================
I: Request Identifiers:
I:
I: # Dicom-Data-Set
I: # Used TransferSyntax: Little Endian Explicit
I: (0008,0052) CS [PATIENT]                                #   8, 1 QueryRetrieveLevel
I: (0010,0020) LO [1752]                                #   8, 1 PatientID
I:
E: Move Request Failed: 0006:0317 Peer aborted Association (or never connected)
I: Peer Aborted Association

[Markus Sabin]

It seems that the Move SCP you are talking to just closes the association while it should better return a C-MOVE-Response which is helpful for debugging. But a few guesses of what typically goes wrong in C-MOVE:


- the Move Destintation (testAET) must be configured on the Move SCP side. It should resolve to your IP address and Port 108
- If it is a large object (US MF), it may be encoded with lossy compression. If your Storage SCP (on port 108) forces the Storage SCU to decompress the image, this might fail. So playing with the network transfer options could help. My first guess would be that +xy is the parameter needed.

If possible I would look into the logs of the PACS first.

[cappa1983]

Thanks for the info, Markus!

I was able to set the +xy flag and it did download the USMF as JPEG Baseline. I also used the +xa and it showed JPEG Baseline so my assumption is that it was stored that way in the PACS.

Strangely enough, I ran an instance of storescp and set it for Implicit Little Endian, and initiated the move using movescu, and about 60 seconds in, movescu gave me the same two lines:

Code: Select all

E: Move Request Failed: 0006:0317 Peer aborted Association (or never connected)
I: Peer Aborted Association

but, the storescp still processed the full request for the USMF study for ILE and the ~3GB study was downloaded.

The SCP PACS is running DCM4CHEE and the log showed a "connection refused" message when trying to send the SOP UID, when movescu shows the "peer aborted assocation" message.

any thoughts on why storescp would download the full study, but movescu shows the peer aborted message whether or not you download the study using just movescu, or in combination with storescp?

I'm looking to download the study as ILE or ELE instead of other compressed TR's.

thanks!