fo-dicom Processing failure while printing

When sending images to a DICOM printer, some fail to get delivered. For example out of 4 images only 3 appear in the final print. The code used to send the images largely follows the one in fo-dicom examples. It seem to fail before or inside the DicomNCreateRequest.OnResponseReceived handler. Here's the log, please see the Processing failure line:

Implementation Version: AGFA DTF1.0.90 Maximum PDU Length: 65542 Async Ops Invoked: 1 Async Ops Performed: 1 Presentation Contexts: 4 Presentation Context: 1 [Accept] Abstract Syntax: Basic Grayscale Print Management Meta SOP Class Transfer Syntax: Implicit VR Little Endian: Default Transfer Syntax for DICOM Presentation Context: 3 [Accept] Abstract Syntax: Basic Color Print Management Meta SOP Class Transfer Syntax: Implicit VR Little Endian: Default Transfer Syntax for DICOM Presentation Context: 5 [Accept] Abstract Syntax: Basic Grayscale Print Management Meta SOP Class Transfer Syntax: Explicit VR Little Endian Presentation Context: 7 [Accept] Abstract Syntax: Printer SOP Class Transfer Syntax: Explicit VR Little Endian 2021-08-20 11:47:30.1812|INFO|Dicom.Network|DS4500 -> N-Create request [104] 2021-08-20 11:47:30.5909|INFO|Dicom.Network|DS4500 <- N-Create response [104]: Success 2021-08-20 11:47:30.5909|INFO|Dicom.Network|DS4500 -> N-Create request [105] 2021-08-20 11:47:30.7059|INFO|Dicom.Network|DS4500 <- N-Create response [105]: Success 2021-08-20 11:47:30.7059|INFO|Dicom.Network|DS4500 -> N-Set request [106] 2021-08-20 11:47:31.1836|WARN|Dicom.Network|Waited 1 second to cleanup but completion flag is still not set. Trying to flush next message 2021-08-20 11:47:31.4704|INFO|Dicom.Network|DS4500 <- N-Set response [106]: Processing failure 2021-08-20 11:47:31.4704|INFO|Dicom.Network|DS4500 -> N-Action request [107] Action Type: 0001 2021-08-20 11:47:31.5194|INFO|Dicom.Network|DS4500 <- N-Action response [107]: Film box SOP instance hierarchy does not contain image box SOP instances (empty page)

Could you please help me with 2 questions:

Where does the DS4500 <- N-Set response [106]: Processing failure message point as the most likely source of the problem: something inside of fo-dicom; or the problem is with image box set request handling?
What Waited 1 second to cleanup but completion flag is still not set. Trying to flush next message tries to tell us?

Environment Fellow Oak DICOM version: 4.0.4 OS: Windows 10 x64 (most likely) Platform: e.g. .NET Framework 4.7.2

Sep 15 '21 17:09 miscigor

Here's the log from 4 images, only the last 3 appear in print:

Implementation Class: Unknown [1.3.51.0.1.3] Implementation Version: AGFA DTF1.0.90 Maximum PDU Length: 65542 Async Ops Invoked: 1 Async Ops Performed: 1 Presentation Contexts: 4 Presentation Context: 1 [Accept] Abstract Syntax: Basic Grayscale Print Management Meta SOP Class Transfer Syntax: Implicit VR Little Endian: Default Transfer Syntax for DICOM Presentation Context: 3 [Accept] Abstract Syntax: Basic Color Print Management Meta SOP Class Transfer Syntax: Implicit VR Little Endian: Default Transfer Syntax for DICOM Presentation Context: 5 [Accept] Abstract Syntax: Basic Grayscale Print Management Meta SOP Class Transfer Syntax: Explicit VR Little Endian Presentation Context: 7 [Accept] Abstract Syntax: Printer SOP Class Transfer Syntax: Explicit VR Little Endian 2021-08-20 11:36:49.6029|INFO|Dicom.Network|DS4500 -> N-Create request [82] 2021-08-20 11:36:49.9307|INFO|Dicom.Network|DS4500 <- N-Create response [82]: Success 2021-08-20 11:36:49.9307|INFO|Dicom.Network|DS4500 -> N-Create request [83] 2021-08-20 11:36:50.0157|INFO|Dicom.Network|DS4500 <- N-Create response [83]: Success 2021-08-20 11:36:50.0157|INFO|Dicom.Network|DS4500 -> N-Set request [84] 2021-08-20 11:36:50.5793|INFO|Dicom.Network|DS4500 <- N-Set response [84]: Processing failure 2021-08-20 11:36:50.5793|INFO|Dicom.Network|DS4500 -> N-Set request [85] 2021-08-20 11:36:50.6053|WARN|Dicom.Network|Waited 1 second to cleanup but completion flag is still not set. Trying to flush next message 2021-08-20 11:36:51.3269|INFO|Dicom.Network|DS4500 <- N-Set response [85]: Success 2021-08-20 11:36:51.3269|INFO|Dicom.Network|DS4500 -> N-Set request [86] 2021-08-20 11:36:51.6067|WARN|Dicom.Network|Waited 1 second to cleanup but completion flag is still not set. Trying to flush next message 2021-08-20 11:36:51.7736|INFO|Dicom.Network|DS4500 <- N-Set response [86]: Success 2021-08-20 11:36:51.7746|INFO|Dicom.Network|DS4500 -> N-Set request [87] 2021-08-20 11:36:52.3482|INFO|Dicom.Network|DS4500 <- N-Set response [87]: Success 2021-08-20 11:36:52.3482|INFO|Dicom.Network|DS4500 -> N-Action request [88] Action Type: 0001 2021-08-20 11:36:52.6191|WARN|Dicom.Network|Waited 1 second to cleanup but completion flag is still not set. Trying to flush next message 2021-08-20 11:36:52.7680|INFO|Dicom.Network|DS4500 <- N-Action response [88]: Success Action Type: 0000

Sep 16 '21 06:09 miscigor

Additional info: might be related to https://github.com/fo-dicom/fo-dicom-samples/issues/28, since B603 is happening on the printer side here too. What might be a potential strategy for dealing with such a situation?

Sep 20 '21 11:09 miscigor

I do not know. Getting "Processing failure" from the server is very little information. The only strategy for dealing with such an information, is, to ask the technican on the printer side for some log, or for some more information what kind of processing failure had happened.

Oct 03 '22 07:10 gofal

Did you manage to get some further informations from the printers log?

Nov 22 '22 15:11 gofal

closing this issue due to inactivity. If you still have this issue with latest version of fo-dicom, feel free to reopen this issue and provide actual information.

Mar 31 '24 20:03 gofal