OHIF Viewer DIMSE fail


I wanted to set up the OHIF viewer using the DIMSE connection config, but get an error when trying to retrieve study. Loading the study list in OHIF works fine.

In the Orthanc logs I only get "C-FIND request handler has failed: Internal error". Not further information, also when starting with --trace.

In the OHIF log I get this:
Connection established
I20170107-10:55:07.341(1)? ==Associated
I20170107-10:55:07.344(1)? Sending command C-FIND-RQ
I20170107-10:55:07.359(1)? message failed with status c000
I20170107-10:55:07.360(1)? Connection closed

Of course I dded the OHIFDCM AET to Orthanc config.
BTW, using OHIF with DICOMWeb works fine, but is slower when loading the study list.

Does anyone have any idea what's going wrong?


Some new information on this issue:

After switching from mainline to Orthanc 1.2 (Osimis build, Mac), I get this error message:

E0116 10:33:19.483744 FromDcmtkBridge.cpp:1649] While creating a DICOM instance, tag (0018,9327) has out-of-range value: ""
E0116 10:33:19.483960 FindScp.cpp:256] C-FIND request handler has failed: Bad file format

Any workaround?

I would say your DICOM file is invalid: (0018,9327) should be a floating point and can not be empty in some cases (http://dicom.nema.org/medical/dicom/2014c/output/chtml/part03/sect_C. Therefore, Orthanc does not accept to return it in a C-Find response.

You may sanitize your files before pushing them to Orthanc or, eventually, when Orthanc receives them with a Lua callback OnStoredInstance (check this sample: https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Samples/Lua/ModifyInstanceWithSequence.lua?at=default&fileviewer=file-view-default)

I doubt it. The message also appears when opening a CR study, where the tag isn't even present!

I'm getting same error message. I have posted performance issue with OHIF. Please see my post.

I'm using Orthanc 1.2.


Best regards,


Any news on this specific issue after posting to the OHIF mailing list?

Erik Ziegler writes there: “I am using Orthanc with DIMSE daily, so I can confirm that it works perfectly fine if you have properly configured both Orthanc and the OHIF Viewer.” This seems to indicate that your issue is specific to the DR images you make use of.

Back to the following error log: