Error - Failed to open file.

bebo109 · Post by **bebo109** » Wed Oct 23, 2013 10:36 pm

I just installed the PacsOne server as an evaluation on Windows 7 with apache 2.2 and PHP 5.3. But I am running into a problem which I cant seem to solve on my own.

After successfully connecting to the PacsOne server using a Pacs Client. I open a Dicom CD. I then Send the study to the pacs server. (This works perfectly fine; The files get created and everything seems to work fine with no errors).
When I try to then download the study I get an error on my client. I then take a look at the logs on the PacsOne Server and I notice this error. How do I resolve this issue?
I don't think its a rights issue because I am able to "Send to Pacs" just fine (Also I set the security rights for the folder and all child objects with "Everyone" and with all rights.

This is the error:
Wed Oct 23 15:05:35 2013 INFO - <7> C-STORE [3] command received in P-DATA-TF PDU
Wed Oct 23 15:05:35 2013 ERROR - Failed to open file [C:/Program Files (x86)/PacsOne/php/PacsOne Archive/2013-10-23-WED/1.2.840.113663.1500.1.218623263.3.9.20080216.103431.546.DCM] for SOP instance: 1.2.840.113663.1500.1.218623263.3.9.20080216.103431.546

Post by **pacsone** » Thu Oct 24, 2013 3:51 pm

Did you check if that specific storage directory "C:/Program Files (x86)/PacsOne/php/PacsOne Archive/" does exist, and if the user account PacsOne Server service is currently running as has sufficient privileges to write/create files under that directory?

bebo109 · Post by **bebo109** » Thu Oct 24, 2013 6:14 pm

pacsone wrote:Did you check if that specific storage directory "C:/Program Files (x86)/PacsOne/php/PacsOne Archive/" does exist, and if the user account PacsOne Server service is currently running as has sufficient privileges to write/create files under that directory?

Yes, the directory and the file exist.
Yes, the user account PacsOne Server service is using has full control over the folder and its contents.

What else should I do?

bebo109 · Post by **bebo109** » Thu Oct 24, 2013 7:06 pm

Ok, it is not a read write issue.
There is a problem with the original content. some Dicom images work and some don't.

it seems to me that any image with a cine loop sequence DO NOT WORK.

Can you provide any feedback on this? Is there a way to fix this?

bebo109 · Post by **bebo109** » Thu Oct 24, 2013 8:19 pm

Forget my last post. That was an incorrect assumption...

This should provide some insight for you to help me.

I have a DCM file which I am able to open with microDicom (dicom viewer).
I then upload this working DCM file to the pacs server using a pacs client. (I’ve tried K-Pacs, and GinkgoCADx).
I then try to open the DCM file from the PacsOne archive folder using microDicom. (I get an error, unable to open file).
So, the problem seems to be that PacsOne may be converting it incorrectly when uploading the dcm?

Can you provide any feedback?

bebo109 · Post by **bebo109** » Thu Oct 24, 2013 8:53 pm

Am I going to get any support?

Post by **pacsone** » Fri Oct 25, 2013 6:14 pm

You should NOT open the raw Dicom image files stored by PacsOne Server directly via the Windows File Explorer, because PacsOne is a PACS application which means all images received by PacsOne will be stored on a remote server (or even in the cloud). So it does not make any sense to access the raw Dicom image files under the file system on the remote server/cloud. Instead, you should be accessing the patients/studies/series/images stored in the PacsOne Server database via a web browser from anywhere:

http://localhost/pacsone/home.php

Replace the "localhost" with the remote server name or DNS name if you are running the web browser from a client PC.

bebo109 · Post by **bebo109** » Fri Oct 25, 2013 7:06 pm

Ok, that makes perfect sense. But i think you might be forgetting that i am simply trying to troubleshoot the "ERROR - Failed to open file" issue.

You have provided me with NO support.

Even when i goto http://localhost/pacsone/home.php and locate the study. I simply see a red "Stop" thumbnail for the dicom file.
THE WEBVIEWER DOESNT DISPLAY IT, MY PACS CLIENT WILL NOT DOWNLOAD, AND I CAN NOT OPEN THE INDIVIDUAL DCM FILES (FOR TROUBLESHOOTING PURPOSES) AFTER THEY ARE ON THE SERVER.

Can you provide me with any troubleshooting steps?

Post by **pacsone** » Mon Oct 28, 2013 5:03 pm

The "ERROR - Failed to open file" error you posted previously was logged when PacsOne was receiving an incoming image, so it has nothing to do with the issue when you tried to download/retrieve the study. BTW, what's the exact error you got when you tried to download the study from your PACS client?

About the STOP signs, can you click on the URL link underneath any of the STOP signs displayed? The resulting page will display the full path to the raw Dicom image file on the server where PacsOne stores that image, and you can check and verify if the raw image file is still there or not.

bebo109 · Post by **bebo109** » Tue Oct 29, 2013 5:42 pm

I'm sorry to say. But you are wrong... Please re-read my original post. I stated that while the PacsOne was receiving an incoming image; EVERYTHING WORKED FINE. The error Message occurs when i download/retrieve the study.

About the raw image file. I already stated that the directory and the file are in the correct location.

So once again. The exact error message when i tried to download/retrieve a study is:
Wed Oct 23 15:05:35 2013 INFO - <7> C-STORE [3] command received in P-DATA-TF PDU
Wed Oct 23 15:05:35 2013 ERROR - Failed to open file [C:/Program Files (x86)/PacsOne/php/PacsOne Archive/2013-10-23-WED/1.2.840.113663.1500.1.218623263.3.9.20080216.103431.546.DCM] for SOP instance: 1.2.840.113663.1500.1.218623263.3.9.20080216.103431.546

Post by **pacsone** » Wed Oct 30, 2013 4:40 pm

What exactly do you mean by "when i download/retrieve the study" below? If you were trying to retrieve images, then PacsOne should have logged either a C-FIND or C-MOVE command, but not the C-STORE command you posed below:

Wed Oct 23 15:05:35 2013 INFO - <7> C-STORE [3] command received in P-DATA-TF PDU
Wed Oct 23 15:05:35 2013 ERROR - Failed to open file [C:/Program Files (x86)/PacsOne/php/PacsOne Archive/2013-10-23-WED/1.2.840.113663.1500.1.218623263.3.9.20080216.103431.546.DCM] for SOP instance: 1.2.840.113663.1500.1.218623263.3.9.20080216.103431.546

So please elaborate on exactly how you were downloading the images.

bebo109 · Post by **bebo109** » Wed Oct 30, 2013 5:35 pm

Ok. I will elaborate...

I tried this with several different clients. 2 which i remember are Ginkgo Cadx and the other is KPacs.

From the client i first query for a patient id.
It retrieves a list of the patient which i am looking for successfully.
I then simply double click the list item so that i can view them. This is when i get the error.

Its that simple.

A few more things i would like to mention... You say PacsOne SHOULD have logged something other than the C-STORE command. The whole problem here is that PacsOne is not working the way it SHOULD.

I have since moved on from PacsOne and i am now working with Conquest DICOM software 1.4.17. This works as it SHOULD. I have run into no issues with it.

Post by **pacsone** » Thu Oct 31, 2013 4:16 pm

We appreciate you spending the extra time on this post after you've moved on to Conquest, but the logs you posed were clearly not from either a Dicom Query or Retrieve command sent from either of your clients. So we cannot be of further help if you don't provide the information we requested.

Nana111 · Post by **Nana111** » Mon Jan 27, 2014 3:20 am

HI there
There are so many useful information here.As for dicom,i think a DICOM Decoder Control would help a lot. aimed to decode DICOM images and extract messages that are referenced in the DICOM metadata. DICOM (short for Digital Imaging and Communications in Medicine) is a common image file format that is specifically used to encode medical images and patient information. Using this DICOM medical image reading control image SDK, .NET developers can easily and quickly view and decode all versions of DICOM formats by Visual C# programming code.

PacsOne Server

Error - Failed to open file.

What now?

Found problem.

Learned More.

Support

Makes Sense... BUT...