Bug 219 - Cannot request a instance
Summary: Cannot request a instance
Status: RESOLVED FIXED
Alias: None
Product: Orthanc
Classification: Unclassified
Component: Plugin - DICOMweb (show other bugs)
Version: unspecified
Hardware: PC Linux
: Highest blocker
Assignee: Sébastien Jodogne
URL:
Depends on:
Blocks:
 
Reported: 2023-09-28 04:35 CEST by Pinkman
Modified: 2024-01-24 13:30 CET (History)
1 user (show)

See Also:


Attachments
attachment include: one dcm file of problem data, a log file, a request screenshot, output of dciodvfy tool. (364.32 KB, application/zip)
2023-09-28 04:35 CEST, Pinkman
Details
dcm file (338.43 KB, application/dicom)
2024-01-24 10:10 CET, Pinkman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pinkman 2023-09-28 04:35:50 CEST
Created attachment 127 [details]
attachment include: one dcm file of problem data, a log file, a request screenshot, output of dciodvfy tool.

Please carefully read the following page before asking support:
https://book.orthanc-server.com/users/support.html

Also, make sure you have read the FAQ, especially the 'Troubleshooting' and 'Troubleshooting DICOM communications' sections:
https://book.orthanc-server.com/faq.html

**What steps will reproduce the problem?**

When I using dicom-web API `\dicom-web/studies/{study_instance_uid}/series/{series_instance_uid}/intances/{SOP_instance_uid}/frame/1`, I got a 500 status Internal Server Error response(screenshot in attachment). The request headers are in screenshot as well. I also attached docker container logs.

**What is the expected output? What do you see instead?**

Output is none, just error response. I used DICOM standard check tool `dciodvfy`, but I didn't see any problem in this tool's output(screenshot in attachment).

**What version of the product are you using? On what operating system?**

Until 2023.09.27, I am using the latest version orthanc docker image, and my operating system is Deepin 20.7. However I got this problem on my server as well, which operating system is CentOS 7.9.

**Please provide sample, possibly anonymized, DICOM files**
Comment 1 Alain Mazy 2024-01-22 17:52:16 CET
Just tried to reproduce on my system (running latest Orthanc 1.12.2 and DICOMWeb plugin 1.16).
I ran this command:

curl -H "Accept: multipart/related;type=application/octet-stream;transfer-syntax=*" http://localhost:8043/dicom-web/studies/1.2.840.113619.186.80861654864.20191127093640906.664/series/1.3.12.2.1107.5.2.31.30764.2019112909051571929015528.0.0.0/instances/1.2.276.0.7230010.3.1.4.8323329.19659.1705941792.282412/frames/1 --output /tmp/test.raw

I get no error.

Please test again on your side and, if the issue still happens, provide a full reproducible setup.
Comment 2 Pinkman 2024-01-24 03:35:27 CET
I still got an error, here is my side response:

(base) yxc@yxc-PC:~$ curl -H "Accept: multipart/related;type=application/octet-stream;transfer-syntax=*" http://localhost:8042/dicom-web/studies/1.2.840.113619.186.80861654864.20191127093640906.664/series/1.3.12.2.1107.5.2.31.30764.2019112909051571929015528.0.0.0/instances/1.3.12.2.1107.5.2.31.30764.2019112909051544604615434/frames/1 --output /tmp/test.raw
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   395  100   395    0     0  87797      0 --:--:-- --:--:-- --:--:-- 98750
(base) yxc@yxc-PC:~$ cat /tmp/test.raw 
{
        "HttpError" : "Internal Server Error",
        "HttpStatus" : 500,
        "Message" : "Internal error",
        "Method" : "GET",
        "OrthancError" : "Internal error",
        "OrthancStatus" : -1,
        "Uri" : "/dicom-web/studies/1.2.840.113619.186.80861654864.20191127093640906.664/series/1.3.12.2.1107.5.2.31.30764.2019112909051571929015528.0.0.0/instances/1.3.12.2.1107.5.2.31.30764.2019112909051544604615434/frames/1"
}
Comment 3 Alain Mazy 2024-01-24 09:35:49 CET
Hi,

But the instance you are testing with is not in the attached files.  So, please share it.

Alain
Comment 4 Pinkman 2024-01-24 10:08:32 CET
Sorry I request a different dcm file before. This time I use the dcm file which is in attachment ZIP file, get same error. But it seems like we got different SOP Instance UID of this dcm file.
 Sop instance uid in my tools is 1.2.276.0.7230010.3.1.4.1681208418.1.1695866049.252888

(base) yxc@yxc-PC:~$ curl -H "Accept: multipart/related;type=application/octet-stream;transfer-syntax=*" http://localhost:8042/dicom-web/studies/1.2.840.113619.186.80861654864.20191127093640906.664/series/1.3.12.2.1107.5.2.31.30764.2019112909051571929015528.0.0.0/instances/1.2.276.0.7230010.3.1.4.1681208418.1.1695866049.252888/frames/1 --output /tmp/test.raw
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   397  100   397    0     0  88104      0 --:--:-- --:--:-- --:--:-- 99250
(base) yxc@yxc-PC:~$ cat /tmp/test.raw 
{
        "HttpError" : "Internal Server Error",
        "HttpStatus" : 500,
        "Message" : "Internal error",
        "Method" : "GET",
        "OrthancError" : "Internal error",
        "OrthancStatus" : -1,
        "Uri" : "/dicom-web/studies/1.2.840.113619.186.80861654864.20191127093640906.664/series/1.3.12.2.1107.5.2.31.30764.2019112909051571929015528.0.0.0/instances/1.2.276.0.7230010.3.1.4.1681208418.1.1695866049.252888/frames/1"
}
Comment 5 Pinkman 2024-01-24 10:09:29 CET
I will post the dcm file again, in case we are using the same file.
Comment 6 Pinkman 2024-01-24 10:10:30 CET
Created attachment 130 [details]
dcm file

sop instance uid is 1.2.276.0.7230010.3.1.4.1681208418.1.1695866049.252888
Comment 7 Alain Mazy 2024-01-24 13:29:59 CET
Thanks !

This has been fixed in this commit: https://orthanc.uclouvain.be/hg/orthanc-dicomweb/rev/a111b79189c2 and will be included in the next official release (no planned date so far)