When trying to export a series from OsiriX into Orthanc, OsiriX reports STOW-RS operation failure. But Orthanc reports no errors (or warnings) and the new series itself does get properly stored in Orthanc as far as I can tell.
I’m probably overlooking something trivial and it’s probably OsiriX related, so I’d like to ask for help.
I’m running docker jodogne/orthanc-plugins:1.3.2 exposing port 8042 as 9999. OsiriX is configured to access this node as a DICOMweb and points to the /dicom-web path (and the orthanc:orthanc user from the stock configuration).
What version of Osirix are you using? I have the same issue (only when I send through WADO) in 9.5.2 Osirix version.
That happens all the time. I was going to test it on other Osirix version.
Pawel
W dniu środa, 25 lipca 2018 20:32:01 UTC+2 użytkownik Luiz Eduardo Guida Valmont napisał:
I’m using “OsiriX MD ANVISA”, which is a version based off of 8.5.2 for brazilian hospitals.
What I came to find out is actually a bug in OsiriX, I suppose. As it is, OsiriX sends “Accept: /” and an XML body and content type header. Orthanc in turn defaults to JSON when it receives “/”. That should be no problem because of the Accept header.
BUT
OsiriX expects an XML response.
How can you see this happening / fix it? Configure a dicomweb node pointing to localhost and a random port, like 8888. Set up a netcat “server” redirecting the output to a file. Fire the export. Edit the capture file to “Accept: application/xml” while also recreating the gzip’ed content. Push that to a running Orthanc while capturing the the response with a netcat. Now set up a final netcat "server that will respond with Orthanc’s response (which should be a proper one for OsiriX to understand). Fire the same export again. OsiriX should accept with no problems.
In our project I will change a few lines in Orthanc so its default is configurable.
Now that I wrote it it sounds overly complicated. And it is in a sense. Come Monday I’ll try and record a video explaining the process. It’ll make things clear.
In any case, if you have any questions (and by the way I wrote, you’ll most certainly have), please do hit reply and write. I’ll gladly answer.
If this works, we could consider adding a configuration option for the DICOMweb plugin to bypass this part of the specification, and force the use of XML answers.
I confirm that the issue exists with the older versions of OsiriX. However the latests and older Osirix’s versions works fine (through WADO) with dcm4chee and one more local-WADO pacs. The problem seems to be connected with Orthanc itself - it exist only with orthanc.
Thank you Luiz for workaround.
Antoine is there a way to view detailed DICOM communication logs in OsiriX (not general ones from GUI/Menu level)?
Security Clause
Please note that the contents of this message including its attachments is the information protected from disclosure. If this message is not meant for you, please be warned that disclosing, copying, publishing or using it or any attachments is prohibited. If you received this message by mistake, please inform sender immediately, send the message back and delete it from your system including all the attachments.
Sebastien - today will give you feedback if release 1.4.2 works fine with the newest version of OsiriX 9.5.2 - Rev. 20180726
Security Clause
Please note that the contents of this message including its attachments is the information protected from disclosure. If this message is not meant for you, please be warned that disclosing, copying, publishing or using it or any attachments is prohibited. If you received this message by mistake, please inform sender immediately, send the message back and delete it from your system including all the attachments.
Sébastien, I have tested provided Orthanc - 1.4.2 release.
The problem still exists. I can send studies with WADO (with success), but in the end, Osirix display Error window with STOW-RS operation failed.
You could try and post full Orthanc logs in “–verbose” mode, together with OsiriX logs, as they might contain useful information: http://book.orthanc-server.com/faq/log.html
