Dicom Query-Retrieve: Error executing PACS import request

[eloc...@gmail.com]

Hello all, we have set up the DQR plugin (version 1.0.1-xpl) in a newly set-up XNAT v1.8.2.2 system. We are able to query the remote system successfully; the XNAT DICOM SCP receiving node (AE Title "CWS1" on port 5754) has been set up with "custom processing enabled." This node is in the table of our remote PACS and has been given permission to query & retrieve via C-MOVE. However, every initiated retrieval has status "FAILED," no data arrives in prearchive, and the dqr.log reads as follows. Can anyone suggest other leads to help track down the cause of this problem?

Much thanks,

Eve

2021-09-07 11:18:14,443 [Thread-155] ERROR org.nrg.xnatx.dqr.events.PacsDequeueThread - Error executing PACS import request.

org.nrg.xnatx.dqr.dicom.command.cmove.CMoveFailureException:

(0000,0002) UI #28 [1.2.840.10008.5.1.4.1.2.2.2] Affected SOP Class UID

(0000,0100) US #2 [32801] Command Field

(0000,0120) US #2 [2] Message ID Being Responded To

(0000,0800) US #2 [257] Command Data Set Type

(0000,0900) US #2 [43009] Status

        at org.nrg.xnatx.dqr.dicom.command.cmove.dcm4che.tool.DqrCMoveDcmQR.move(DqrCMoveDcmQR.java:49)

        at org.nrg.xnatx.dqr.dicom.command.cfind.dcm4che.tool.CFindSCUSpecificLevel.performCMoveOnResults(CFindSCUSpecificLevel.java:200)

        at org.nrg.xnatx.dqr.dicom.command.cfind.dcm4che.tool.CFindSCUSpecificLevel.cfind(CFindSCUSpecificLevel.java:96)

        at org.nrg.xnatx.dqr.dicom.command.cmove.dcm4che.tool.CMoveSCUSeriesLevel.cmove(CMoveSCUSeriesLevel.java:28)

        at org.nrg.xnatx.dqr.dicom.command.cmove.dcm4che.tool.Dcm4cheToolCMoveSCU.cmoveSeries(Dcm4cheToolCMoveSCU.java:39)

        at org.nrg.xnatx.dqr.services.impl.basic.BasicDicomQueryRetrieveService.importFromPacsRequest(BasicDicomQueryRetrieveService.java:269)

        at org.nrg.xnatx.dqr.events.PacsDequeueThread.runTask(PacsDequeueThread.java:144)

        at org.nrg.xnat.task.AbstractXnatRunnable.run(AbstractXnatRunnable.java:33)

        at java.lang.Thread.run(Thread.java:748)

 

[Steve Moore]

When you see a DICOM error like that, it often means the PACS is unhappy about something. You should see if there is log information on that side to see why it is returning that error.

Steve Moore

[eloc...@gmail.com]

Thank you very much Steve. I am following up with our PACS admins. 

Best,

Eve

[eloc...@gmail.com]

Would there potentially be a problem if the querying AE title in the DQR is the same as the AE for the receiving node in the C-MOVE?

[eloc...@gmail.com]

For anyone's future reference, the response code:

(0000,0900) US #2 [43009] Status

Corresponds to C-MOVE query status: 0xa801, “Move Destination Unknown.”  

“The Move SCP doesn't know the details of the Store SCP so the C-MOVE fails without any attempt to send any C-STORE requests” https://github.com/pydicom/pynetdicom/issues/358#issuecomment-498893050

[Herrick, Rick]

That shouldn’t be a problem for XNAT that I know of. That sounds like you need to register the IP/AE/port of your XNAT with your PACS. At least, I know you have to do that with Orthanc or it won’t respond at all.

 

-- 

Rick Herrick

XNAT Architect/Developer

Computational Imaging Laboratory

Washington University School of Medicine

 

 

From: xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of eloc...@gmail.com <eloc...@gmail.com>
Date: Tuesday, September 7, 2021 at 1:06 PM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] Re: Dicom Query-Retrieve: Error executing PACS import request

* External Email - Caution *

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/b48b39f2-b780-4ef3-94c0-cee287176e88n%40googlegroups.com.

 

---

The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.

[eloc...@gmail.com]

Thanks again, Rick & Steve, your instincts were correct: there was one minor setting our PACS (MIM) admins were overlooking at their end that would enable it to properly acknowledge our receiving XNAT node as a valid C-MOVE destination. With some persistence we hunted it down and now the plugin is working as intended.  

Cheers,

Eve