Dicom Push error, with DQR XNATv1.8.3

[Daniel Beasley]

Hi all,

We have a dockerised XNAT with DQR, tomcat 9 etc. We have several dicom recievrs, only one set up for dqr. We get a similar C-STORE error as onother thread, however we cannot even dicom push locally to a standard dicom receiver (no cusotm processing etc), everything looks correct. Also, it used to work. I'm wondering if a dqr request is stuck as the log contains a dqr error - even though it is to a standard receiver.The dicom.log error (apologies for image instead of text, but hard to copy):

Many thanks,

Dan

[Moore, Charlie]

Hi Dan,

My guess is you had an older pre-release version of DQR installed at some point, right? That would have cached an archive processor in the database which changed when the first release of DQR came out. Assuming that's correct, I think the fix should be to delete the old archive processor. Take a look at this thread here: https://groups.google.com/g/xnat_discussion/c/zYe88W7RqA8/m/_IWe0uZxAQAJ . You can probably skip to the last 8 or so messages. In that thread, I included a REST call to check the site processor list. If you can confirm you have the old processor in that list, Rick and I mentioned some ways in that thread to remove it.

Thanks,

Charlie

---

From: xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of Daniel Beasley <dgd...@gmail.com>
Sent: Wednesday, October 20, 2021 5:34 AM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] Dicom Push error, with DQR XNATv1.8.3

 

* 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/fca527b3-5676-409f-913b-aca82391ba9fn%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.

[Daniel Beasley]

Hi Charlie,

Many thanks, it worked!

Many thanks,

Dan