Error in receiving Multiframe image

[newuser]

I am using Ultrasound machine to send regular(single frame) and multiframe images,
and use dcmscp as server to receive these files.
The command line I used was: dcmscp +xy --config --filename.cfg
The order of sending these 3 images are: regular(902KB), multiframe(17MB), regular(902KB).

It output "Association aborted" message right after received the multiframe image
and cann't accept the third image.

Here is the error message:
////////////////////////////////////////////////////////////////////////////////
.DIMSE receiveFileData: 4188 bytes read (last: NO)
.DIMSE receiveFileData: 0 bytes read (last: YES)
.
*** DB ALERT: attempt to seek beyond 33554432 bytes
Sending:
C-Store RSP: MsgID: 56 [Status=Success]
AffectedSOPClassUID: =UltrasoundImageStorage
AffectedSOPInstanceUID: 1.2.410.200001.1.4000.1.2006022714301674.1.3
Data Set: Not Present
DIMSE Command To Send:

# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0000,0000) UL 0 # 4, 1 CommandGroupLen
gth
(0000,0002) UI =UltrasoundImageStorage # 28, 1 AffectedSOPClas
sUID
(0000,0100) US 32769 # 2, 1 CommandField
(0000,0120) US 56 # 2, 1 MessageIDBeingR
espondedTo
(0000,0800) US 257 # 2, 1 DataSetType
(0000,0900) US 0 # 2, 1 Status
(0000,1000) UI [1.2.410.200001.1.4000.1.2006022714301674.1.3] # 44, 1 AffectedS
OPInstanceUID
DIMSE sendDcmDataset: sending 140 bytes
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (140 bytes), presID=3
DIMSE Command Received:

# Dicom-Data-Set
# Used TransferSyntax: LittleEndianImplicit
(0000,0002) UI =UltrasoundMultiframeImageStorage # 28, 1 AffectedSOPClas
sUID
(0000,0100) US 1 # 2, 1 CommandField
(0000,0110) US 57 # 2, 1 MessageID
(0000,0700) US 0 # 2, 1 Priority
(0000,0800) US 0 # 2, 1 DataSetType
(0000,1000) UI [1.2.410.200001.1.4000.1.2006022714301674.1.4] # 44, 1 AffectedS
OPInstanceUID
Received Store SCP: C-Store RQ: MsgID: 57
AffectedSOPClassUID: =UltrasoundMultiframeImageStorage
AffectedSOPInstanceUID: 1.2.410.200001.1.4000.1.2006022714301674.1.4
Priority: 0
Data Set: Present
RECV:DIMSE receiveFileData: 1204 bytes read (last: NO)
.DIMSE receiveFileData: 65530 bytes read (last: NO)
.DIMSE receiveFileData: 65530 bytes read (last: NO)
.DIMSE receiveFileData: 65530 bytes read (last: NO)
...................................................
.......(Hundreds lines here, they are same as above line)
.DIMSE receiveFileData: 65530 bytes read (last: NO)
.DIMSE receiveFileData: 65530 bytes read (last: NO)
.DIMSE receiveFileData: 34316 bytes read (last: NO)
.DIMSE receiveFileData: 0 bytes read (last: YES)
.
*** DB ALERT: attempt to seek beyond 33554432 bytes
Sending:
C-Store RSP: MsgID: 57 [Status=Success]
AffectedSOPClassUID: =UltrasoundMultiframeImageStorage
AffectedSOPInstanceUID: 1.2.410.200001.1.4000.1.2006022714301674.1.4
Data Set: Not Present
DIMSE Command To Send:

# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0000,0000) UL 0 # 4, 1 CommandGroupLen
gth
(0000,0002) UI =UltrasoundMultiframeImageStorage # 28, 1 AffectedSOPClas
sUID
(0000,0100) US 32769 # 2, 1 CommandField
(0000,0120) US 57 # 2, 1 MessageIDBeingR
espondedTo
(0000,0800) US 257 # 2, 1 DataSetType
(0000,0900) US 0 # 2, 1 Status
(0000,1000) UI [1.2.410.200001.1.4000.1.2006022714301674.1.4] # 44, 1 AffectedS
OPInstanceUID
DIMSE sendDcmDataset: sending 140 bytes
DIMSE receiveCommand
Association Aborted
////////////////////////////////////////////////////////////////////////

But if I use storescu.exe to send these three images one by one, there is no error messages.
It says association released right after received Multiframe images. Why when use Ultrasound
machine send these 3 together, it doesn't work?
Does anyone know the reason? Thanks

[Marco Eichelberg]

The log shows that the association is aborted by the SCU, i.e., the ultrasound machine. However, since all communication up to that point worked fine (no errors), it is not clear from the log why the SCU has aborted the association. From the perspective of the dcmqrscp tool, this happens "suddenly" without explanation.

[Markus Sabin]

Just a guess: The images to be transferred are lossy compressed multiframe images. By default, the transfersyntax accepted by the OFFIS SCP is LittleEndian, so the SCU has to decompress the image before sending. This might fail due to a lack of memory, the SCU crashes and the socket gets lost.

[newuser]

Hi Marco :
Thank you.
That was all the information I can got. It works fine if I send multiframe image use the storescu.exe by this command line : storescu -xy -v localhost filename.dcm and use dcmscp to receive it by this command line : dcmscp +xy -v --config --filename.cfg
why it has DB alert? all files together are less than 32MB. Shouldn't exceed the max limit.


Hi Markus:
Thank you.
If the default transfer syntax is little Endia, but in the commandline I add +xy option, that
means use JPEGbaseline transfer syntax. why it doesn't work?



Does anyone has experience of sending the multiframe image by ultrasound and receiveing it by dcmscp sucessfully?

Thanks

[Markus Sabin]

Hi Markus:
Thank you.
If the default transfer syntax is little Endia, but in the commandline I add +xy option, that
means use JPEGbaseline transfer syntax. why it doesn't work?

Hard to tell without knowing the details. You can use the options -d -v to log the presentation context negotiation. Then you can also see, which transfersyntax is actually selected for the transfer of the images.

[newuser]

The above error message I posted is already outputed by add -v, -d options in command line.

Here are two set of messages output by use two different methods. I think the transfer syntax are same for both methods. So I think the transfer syntax is fine. The difference between these two are there is a DB ALERT message in second method and the last message line is Association Aborted not Association Release. So this causes the file didn't recevied. But why it was aborted?



/*Method 1: Multiframe image sent by storescu and received by dcmscp//
//*commandline used to send: storescu -xy -v localhost image.dcm //
//*command line used to receive: dcmscp +xy -v -d --config cfg.cfg //

...............
count presentation contexts=124
Context ID: 249 (Accepted)
Abstract Syntax: =XRayRadiationDoseSR
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Accepted Transfer Syntax: =JPEGBaseline
count presentation contexts=125
Context ID: 251 (Accepted)
Abstract Syntax: =XRayRadiationDoseSR
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Accepted Transfer Syntax: =LittleEndianExplicit
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (142 bytes), presID=221
DIMSE Command Received:

# Dicom-Data-Set
# Used TransferSyntax: LittleEndianImplicit
(0000,0002) UI =UltrasoundMultiframeImageStorage # 28, 1 AffectedSOPClas
sUID
(0000,0100) US 1 # 2, 1 CommandField
(0000,0110) US 1 # 2, 1 MessageID
(0000,0700) US 2 # 2, 1 Priority
(0000,0800) US 1 # 2, 1 DataSetType
(0000,1000) UI [1.2.410.200001.1.4000.1.20051028104843207.1.5] # 46, 1 Affected
SOPInstanceUID
Received Store SCP: C-Store RQ: MsgID: 1
AffectedSOPClassUID: =UltrasoundMultiframeImageStorage
AffectedSOPInstanceUID: 1.2.410.200001.1.4000.1.20051028104843207.1.5
Priority: 2
Data Set: Present
RECV:DIMSE receiveFileData: 65524 bytes read (last: NO)
.DIMSE receiveFileData: 65524 bytes read (last: NO)
.DIMSE receiveFileData: 65524 bytes read (last: NO)
.............................................
.............................................
.DIMSE receiveFileData: 65524 bytes read (last: NO)
.DIMSE receiveFileData: 15846 bytes read (last: YES)
.
Sending:
C-Store RSP: MsgID: 1 [Status=Success]
AffectedSOPClassUID: =UltrasoundMultiframeImageStorage
AffectedSOPInstanceUID: 1.2.410.200001.1.4000.1.20051028104843207.1.5
Data Set: Not Present
DIMSE Command To Send:

# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0000,0000) UL 0 # 4, 1 CommandGroupLen
gth
(0000,0002) UI =UltrasoundMultiframeImageStorage # 28, 1 AffectedSOPClas
sUID
(0000,0100) US 32769 # 2, 1 CommandField
(0000,0120) US 1 # 2, 1 MessageIDBeingR
espondedTo
(0000,0800) US 257 # 2, 1 DataSetType
(0000,0900) US 0 # 2, 1 Status
(0000,1000) UI [1.2.410.200001.1.4000.1.20051028104843207.1.5] # 46, 1 Affected
SOPInstanceUID
DIMSE sendDcmDataset: sending 142 bytes
DIMSE receiveCommand
Association Release.

#############################################

//* Method 2: Multiframe image sent by Ultrasound machine and received by dcmscp //
//*command line used to receive: dcmscp +xy -v -d --config cfg.cfg //

.............
DIMSE receiveCommand: 1 pdv's (140 bytes), presID=3
DIMSE Command Received:

# Dicom-Data-Set
# Used TransferSyntax: LittleEndianImplicit
(0000,0002) UI =UltrasoundMultiframeImageStorage # 28, 1 AffectedSOPClas
sUID
(0000,0100) US 1 # 2, 1 CommandField
(0000,0110) US 57 # 2, 1 MessageID
(0000,0700) US 0 # 2, 1 Priority
(0000,0800) US 0 # 2, 1 DataSetType
(0000,1000) UI [1.2.410.200001.1.4000.1.2006022714301674.1.4] # 44, 1 AffectedS
OPInstanceUID
Received Store SCP: C-Store RQ: MsgID: 57
AffectedSOPClassUID: =UltrasoundMultiframeImageStorage
AffectedSOPInstanceUID: 1.2.410.200001.1.4000.1.2006022714301674.1.4
Priority: 0
Data Set: Present
RECV:DIMSE receiveFileData: 1204 bytes read (last: NO)
.DIMSE receiveFileData: 65530 bytes read (last: NO)
.DIMSE receiveFileData: 65530 bytes read (last: NO)
...................................................
.......(Hundreds lines here, they are same as above line)
.DIMSE receiveFileData: 65530 bytes read (last: NO)
.DIMSE receiveFileData: 34316 bytes read (last: NO)
.DIMSE receiveFileData: 0 bytes read (last: YES)
.
*** DB ALERT: attempt to seek beyond 33554432 bytes
Sending:
C-Store RSP: MsgID: 57 [Status=Success]
AffectedSOPClassUID: =UltrasoundMultiframeImageStorage
AffectedSOPInstanceUID: 1.2.410.200001.1.4000.1.2006022714301674.1.4
Data Set: Not Present
DIMSE Command To Send:

# Dicom-Data-Set
# Used TransferSyntax: UnknownTransferSyntax
(0000,0000) UL 0 # 4, 1 CommandGroupLen
gth
(0000,0002) UI =UltrasoundMultiframeImageStorage # 28, 1 AffectedSOPClas
sUID
(0000,0100) US 32769 # 2, 1 CommandField
(0000,0120) US 57 # 2, 1 MessageIDBeingR
espondedTo
(0000,0800) US 257 # 2, 1 DataSetType
(0000,0900) US 0 # 2, 1 Status
(0000,1000) UI [1.2.410.200001.1.4000.1.2006022714301674.1.4] # 44, 1 AffectedS
OPInstanceUID
DIMSE sendDcmDataset: sending 140 bytes
DIMSE receiveCommand
Association Aborted //<----- Here aborted, not Released------