Very Computer

by **Alexander Klug** » Mon, 18 Nov 2002 04:54:07

Hello,

has anybody an idea to explain some strange behavior of an Efilm-Radworks
connection:

- Query/Retrieve/Send from Efilm 1.5.3 to 1.5.3 works fine for CR data and
MR studies and series. MR data are mostly from a new Siemens Magnetom,
either MRT->Radworks or MRT->Pacs-archive->Radworks

- Query/Retrieve/Send from Radworks 5.x to Radworks 5.x works fine for the
same data as above.

- Send from PACS or MRI to Radworks works most of the time (there is a bug
in Radworks that brings it to choke on the input data every second day, the
connection and database processes go nuts and increase their memory size
until limit and restart endlessly - until manually killed by special tools
(the Windows task manager has not the required privilege to do this :O )).

- Query from Efilm to Radworks works fine

- Retrieve from Efilm to Radworks or Send from Radworks to Efilm works fine
for single CR images and for single MR images

- Retrieve from Efilm to Radworks or Send from Radworks to Efilm of MR
Studies or images fails. Only the first image of the study is transferred,
the Process is marked pending in the send log of Radworks.

Below you find a transcript using jdicom as a query/retrieve tool because of
its logging capabilities. Behavior of Radworks was the same as if using
efilm alone as described above.

JDicom Q/R had the same AE-Title and the same Port number as Efilm, the
Storage SCP. Even if I used different AE_titles and Port numbers for Query
and the Storage SCP EFILM, there were no difference.

I apologize for the large log below, but if I knew the right place to look
for the cause, I probably wouldn't bother you all. Probably most interesting
are the last few lines of each part.

There are two examples of a retrieve attempt, the first (retrieve of a
series) failed after the first image being transferred, the second (retrieve
of an image) succeeded. First, connection was opened, than an echo
(validation?) was made, the retrieve command followed then.

Thank you in advance!

Alexander

*******************

***An example of the incomplete Retrieve of a MR series

*******************

jdicom: #57:RADWORKS2 << A-ASSOCIATE-RQ PDU jdicom: *** request ***

application context UID: null

called title: RADWORKS2

calling title: AE_XYZ_NEW

max pdu size: 32768

max operation invoked: 1

max operation performed: 1

implementation class UID: 1.2.826.0.1.3680043.2.60.0.1

implementation version Name: softlink_jdt103

abstract syntax scu scp

1.2.840.10008.1.1 -1 -1

1.2.840.10008.5.1.4.1.2.1.1 -1 -1

1.2.840.10008.5.1.4.1.2.2.1 -1 -1

1.2.840.10008.5.1.4.1.2.3.1 -1 -1

1.2.840.10008.5.1.4.1.2.1.2 -1 -1

1.2.840.10008.5.1.4.1.2.2.2 -1 -1

1.2.840.10008.5.1.4.1.2.3.2 -1 -1

nr abstract syntax pcid description

0 1.2.840.10008.1.1 1 Verification SOP Class

ts-0 1.2.840.10008.1.2 Implicit VR Little Endian
Transfer Syntax

1 1.2.840.10008.5.1.4.1.2.1.1 3 Patient Root Query/Retrieve
Information Model - FIND SOP Cl...

ts-0 1.2.840.10008.1.2 Implicit VR Little Endian
Transfer Syntax

2 1.2.840.10008.5.1.4.1.2.2.1 5 Study Root Query/Retrieve
Information Model - FIND SOP Cl...

ts-0 1.2.840.10008.1.2 Implicit VR Little Endian
Transfer Syntax

3 1.2.840.10008.5.1.4.1.2.3.1 7 Patient/Study Only Query/Retrieve
Information Model - FIND SOP Cl...

ts-0 1.2.840.10008.1.2 Implicit VR Little Endian
Transfer Syntax

4 1.2.840.10008.5.1.4.1.2.1.2 9 Patient Root Query/Retrieve
Information Model - MOVE SOP Cl...

ts-0 1.2.840.10008.1.2 Implicit VR Little Endian
Transfer Syntax

5 1.2.840.10008.5.1.4.1.2.2.2 11 Study Root Query/Retrieve
Information Model - MOVE SOP Cl...

ts-0 1.2.840.10008.1.2 Implicit VR Little Endian
Transfer Syntax

6 1.2.840.10008.5.1.4.1.2.3.2 13 Patient/Study Only Query/Retrieve
Information Model - MOVE SOP Cl...

ts-0 1.2.840.10008.1.2 Implicit VR Little Endian
Transfer Syntax

*************** Waiting for AssociationRsp ASSOCIATE_ACKNOWLEDGE detected
jdicom: #57:RADWORKS2 >> A-ASSOCIATE-AC PDU jdicom: *** acknowledge ***

max pdu size: 16384

max operation invoked: 1

max operation performed: 1

implementation class UID: 1.2.528.1.1001.2.19980612.1

implementation version name: AMI_DICOM_40

abstract syntax scu scp

nr pcid result transfer syntax

0 1 accepted 1.2.840.10008.1.2

1 3 accepted 1.2.840.10008.1.2

2 5 accepted 1.2.840.10008.1.2

3 7 user rejection

4 9 accepted 1.2.840.10008.1.2

5 11 accepted 1.2.840.10008.1.2

6 13 user rejection

******************* jdicom: #57:RADWORKS2 << C-MOVE-RQ Study Root
Query/Retrieve Information Model - MOVE SOP Class (0000,0002) UI
[1.2.840.10008.5.1.4.1.2.2.2] # 28 1
AffectedSOPClassUID

(0000,0100) US [33] # 2 1
CommandField

(0000,0110) US [1] # 2 1
MessageID

(0000,0600) AE [AE_XYZ_NEW] # 12 1
MoveDestination

(0000,0700) US [0] # 2 1
Priority

(0000,0800) US [65278] # 2 1
DataSetType

jdicom: #57:RADWORKS2 << Dataset (0008,0052) CS [SERIES]
# 6 1 QueryRetrieveLevel

(0020,000d) UI [1.2.276.0.24.472.158626.8.0] # 28 1
StudyInstanceUID

(0020,000e) UI [1.3.12.2.1107.5.2.12.21927.5.0.11467369369003788]# 48
1 SeriesInstanceUID

jdicom: RADWORKS2 Enter DimseExchange.run() jdicom: RADWORKS2 Waiting for
PDU

jdicom: RADWORKS2 PDU received

jdicom: #57:RADWORKS2 >> C-MOVE-RSP Study Root Query/Retrieve Information
Model - MOVE SOP Class, status #c000H[Failure: Unable to process]

(0000,0002) UI [1.2.840.10008.5.1.4.1.2.2.2] # 28 1
AffectedSOPClassUID

(0000,0100) US [32801] # 2 1
CommandField

(0000,0120) US [1] # 2 1
MessageIDBeingRespondedTo

(0000,0800) US [257] # 2 1
DataSetType

(0000,0900) US [49152] # 2 1
Status

jdicom: RADWORKS2 Waiting for PDU

jdicom: #57:RADWORKS2 << A-RELEASE-RQ PDU

jdicom: RADWORKS2 PDU received

jdicom: #57:RADWORKS2 >> A-RELEASE-RP PDU

jdicom: #57:RADWORKS2 closing socket

jdicom: RADWORKS2 Leave DimseExchange.run()

****************************************************************************
***********

*Example of the successful transfer of a single MR image

****************************************************************************
***********

jdicom: #59:RADWORKS2 << A-ASSOCIATE-RQ PDU jdicom: *** request ***