Associate request aborted?

Jonathan · Post by **Jonathan** » Thu Aug 31, 2006 7:33 am

Every now and then we get the following (not reproducable) error on trying to use the DICOM ToolKit movescu aplpication to send data to the PacsONE Server:

Code: Select all

Wed Aug 30 15:49:12 2006 INFO - Session: <32444> started from SCU: 172.17.4.101
Wed Aug 30 15:49:12 2006 INFO - <32444> Receiving A-ASSOCIATE-RQ PDU
Wed Aug 30 15:49:12 2006 INFO - 1 record found in [applentity] table
Wed Aug 30 15:49:12 2006 INFO - <32444> A-ASSOCIATE-RQ received successfully
Wed Aug 30 15:49:12 2006 INFO - <32444> Sending A-ASSOCIATE-AC PDU
Wed Aug 30 15:49:12 2006 INFO - <32444> A-ASSOCIATE-AC PDU sent successfully
Wed Aug 30 15:49:12 2006 INFO - <32444> Receiving P-DATA-TF PDU
Wed Aug 30 15:49:12 2006 INFO - <32444> C-MOVE [3] command received in P-DATA-TF PDU
Wed Aug 30 15:49:12 2006 INFO - 1 record found in [image] table
Wed Aug 30 15:49:12 2006 INFO - 2 tags processed in CDataSetPdv
Wed Aug 30 15:49:12 2006 INFO - C-STORE Sub-session: <32445> started for SCP: 172.17.4.101 Port: 104
Wed Aug 30 15:49:12 2006 INFO - <32445> Sending A-ASSOCIATE-RQ PDU
Wed Aug 30 15:49:12 2006 INFO - <32445> Waiting for A-ASSOCIATE result
Wed Aug 30 15:49:12 2006 ERROR - <32445> ASSOCIATE-RQ failed, PDU=[3]. Aborting
Wed Aug 30 15:49:12 2006 INFO - Session: <32445> disconnected for client: 172.17.4.101
Wed Aug 30 15:49:12 2006 INFO - <32444> A-ASSOCIATE-RELEASE-RQ PDU received
Wed Aug 30 15:49:12 2006 INFO - <32444> Sending A-ASSOCIATE-RELEASE-RSP PDU
Wed Aug 30 15:49:12 2006 INFO - <32444> A-ASSOCIATE-RELEASE-RSP PDU sent successfully
Wed Aug 30 15:49:12 2006 INFO - Session: <32444> disconnected for client: 172.17.4.101

I have been looking in the DICOM definitions in table 9-21 of Part 8 (PDF page 41) and I am wondering what the 3 bewteen the brackets in PDU[3] means?

Is this the PDU type or the Source or the Reason of the error?
Maybe this will help me pinpoint the source of the error.

Unfortunately I have no extensive log at the moment. Can some one tell me what might be the source of this error?

Post by **pacsone** » Thu Aug 31, 2006 10:44 am

PDU=[3] means the association request sent from PacsOne to that remote AE has been rejected, so you need to make sure that remote AE has configured PacsOne as a valid AE, and has enabled access for PacsOne to send images to it.

Jonathan · Post by **Jonathan** » Thu Aug 31, 2006 11:42 am

pacsone wrote:PDU=[3] means the association request sent from PacsOne to that remote AE has been rejected, so you need to make sure that remote AE has configured PacsOne as a valid AE, and has enabled access for PacsOne to send images to it.

That was my first train of thought indeed. However at the PacsONE side configuration seems to bo valid, the other side is build by a routine using the DCMTK movescu.exe utility.

The big problem is that it won't reproduce, sending the same image again works 99 of 100 times, if we are tying to reproduce the error. After having had the error, resending a few times will solve the problem, without changing any of the parameters.

Post by **pacsone** » Thu Aug 31, 2006 2:41 pm

If the problem only happens occasionally, then it does not look like a configuration issue because if it was, then the problem would be very consistent (either fail or succeed 100% of time).

Does this AE at IP addr 172.17.4.101 Port: 104 has any error log of some sort? It should have logged the reason for rejecting the association request from an external AE (PacsOne), e.g., too many simultaneous connections, database busy, cannot write output file, etc.