Q/R Crashed Orthanc 0.8.5 in Windows 8

[koepsell]

Q/R Crashed Orthanc 0.8.5 in Windows 8

[GoogleCodeExporter]

Hello,

I cannot reproduce your problem, I observe no crash on Q/R against Orthanc 
0.8.5 running under Windows.

Please could you be more specific about your Q/R? Is it the "Q" part or the "R" 
part that leads to the crash? What is the manufacturer of your querying node? 
Could you provide us with a command-line using the standard "findscu" and 
"movescu" standard tools (from DCMTK) to reproduce the problem?

Concretely, here are two command lines that are known to work:

# findscu -P -aec ORTHANC -aet STORESCP 192.168.1.1 4242 -k 0008,0052=PATIENT 
-k PatientName -k PatientID
# movescu -P -aec ORTHANC -aet STORESCP -aem STORESCP 192.168.1.1 4242 -k 
0008,0052=PATIENT -k PatientID=0359491W

In this setup, Orthanc has the AET "ORTHANC", the DICOM port 4242, is running 
on IP address 192.168.1.1, and its configuration file contains the following 
entry:

  "DicomModalities" : {
    "sample" : [ "STORESCP", "192.168.1.2", 2000 ]
  }

Another instance of Orthanc is running on IP 192.168.1.2, port 2000. Could you 
modify this sample setup to provide a problematic version of these command 
lines? TIA!

Original comment by [email protected] on 16 Jan 2015 at 3:40

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have found the problem.

I configured configuration.json as follows:

  "DicomModalities" : {
    "syngo.via" : [ "VIATITLE", "192.168.1.2", 2000 ]
  }

It crashes if there is a "." in the description. Fixed with

  "DicomModalities" : {
    "syngovia" : [ "VIATITLE", "192.168.1.2", 2000 ]
  }

Perhaps I didn't read through the entire document, but I couldn't find this in 
the documentation.

Sorry for misleading the cause to Windows 8.

Original comment by [email protected] on 20 Jan 2015 at 8:21

[GoogleCodeExporter]

OK, thanks! I now close the issue.

Original comment by [email protected] on 20 Jan 2015 at 8:30

• Changed state: Invalid