Store SCP error: DIMSE Failed to receive message

[vipin.vjayan]

Store SCP is failed to receive message over VPN at random images and below is the logs;
It looks like a network issue over VPN, but anyone know what could have been happened here and is there any workaround to handle these types of network errors?
Logs are may be a little different in times but overall it is failed while reading from socket.

Code: Select all

T: DIMSE receiveDataSetInMemory: 16378 bytes read (last: NO)
T: Read PDU HEAD TCP: 87 1c 3f af 4f 76
E: Store SCP Failed: 0006:020c DIMSE Read PDV failed
E: 0006:0321 Unrecognized PDU type: 87
E: DIMSE failure (aborting association): 0006:020c DIMSE Read PDV failed
E: 0006:0321 Unrecognized PDU type: 87
T: DUL  FSM Table: State: 6 Event: 14
T: DUL  Event:  A-ABORT request primitive
T: DUL  Action: AA 1 Send A ABORT PDU
T: Read PDU HEAD TCP: d5 94 e1 dd ab 6d
T: DUL  FSM Table: State: 13 Event: 18
T: DUL  Event:  Unrecognized/invalid PDU
T: DUL  Action: AA 7 State 13 Send Abort

-----------------------------------------------------------------------------------------------------------



Appreciate your time and help.
Thanks

[Michael Onken]

Hi,

I agree that this looks like a VPN issue where the network connection breaks down in the middle of the communication.

If there is a virus scanner running in the background, I would try to disable it for testing. We had cases where this was also a cause of weird connection problems.

Best regards,
Michael

[vipin.vjayan]

Thank you for taking time to read my post and reply.

Unfortunately disabling anti-virus software and even firewall doesn't help me to solve this issue.
Sometimes it takes so long to fail sometimes it failed in first few seconds.
I'm thinking about retrying move request if its failed by this error reason. But it will make things complex as we need to track how many series of the given study was received.

Thanks

[Marco Eichelberg]

In any case. I don't think that you can solve this problem on DCMTK level. The TCP transport connection apparently breaks spontaneously, and the error message only describes what happens in storescp when detecting that the network connection is suddenly gone unexpectedly.