DICOM transfer failed from Prisma "Insufficient resource on remote node"

26 views
Skip to first unread message

Michael Rohan

unread,
Sep 16, 2024, 9:25:40 PM9/16/24
to xnat_discussion
Hi,
As I've been fiddling with the MR Export settings on my Prisma, the DICOM send to my XNAT stopped working. I get an error from the Prisma "Insufficient resource on remote node, X of X objects could not be transferred." I have a development XNAT installation and and trying things out before committing, but this seems odd. The disk is not full. Has anyone seen this before?

Thanks,
Michael Rohan
Laureate Institute

Jenny Gurney

unread,
Sep 20, 2024, 7:32:37 PM9/20/24
to xnat_discussion
I haven't seen it, but things that come to mind to narrow it down:
1. Did you possibly enable TLS on the Prisma DICOM node you set up for your XNAT? XNAT can't do TLS. Any other settings you changed on the Prisma for your XNAT?
2. Make sure you are able to send to the XNAT DICOM receiver on your XNAT from any other tool -- dcmtk dcmsend, for example?
3. Can you ping your development XNAT's IP address from a command prompt on the Prisma console? Maybe there were network changes you weren't aware of..

Michael Rohan

unread,
Sep 20, 2024, 7:36:30 PM9/20/24
to xnat_di...@googlegroups.com
Oddly enough, the reason for this message was that my DICOM autorouting syntax on XNAT was incorrect, I had a typo in it - extra parentheses. This caused XNAT to reject the transfer, and resulted in the unrelated error message. Once the autorouting typo was fixed, all went smoothly.

--
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/dd38d4ae-c505-426a-af07-4897f712567fn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages