Can't upload DICOM Images

skreiner · Post by **skreiner** » Mon Sep 08, 2008 6:08 pm

Hi. I am just getting started with PacsOne. I seem to have everything set up and all seems to be working well. We have just acquired a GE OEC 9900 C-arm which we would like to use in conjunction with PacsOne. I have set it up as an AE in PacsOne with Access Enable. I can ping the device from the PacsOne interface without a problem.

I set PacsOne up as a AE on the OEC 9900. I can ping the PacsOne IP address from the device just fine. Whenever I try to upload an image to the database or connect from the OEC 9900 I get a failure message, essentially saying unable to connect.

Any advice? Me and the GE rep worked for about an hour trying to get it to work.

Post by **pacsone** » Mon Sep 08, 2008 6:29 pm

Did you try a Dicom-ping (C-ECHO) from the GE device to PacsOne Server and see if it can connect to PacsOne at the Dicom message layer?

Another thing you can check is to make sure PacsOne Server is indeed running by checking if you see both PacsOne.exe and PacsOneSrv.exe executables running from the Windows Task Manager on the server where PacsOne is installed (CTL-ALT-DEL, Task Manager->Process List->Show All Processes). If not, then there is a problem with your license as it's either invalid or missing.

skreiner · Post by **skreiner** » Mon Sep 08, 2008 9:08 pm

I am using the Linux version with Ubuntu. I am still in the in evaluation period of the Premium Edition. Will this affect my ability to link with the device?

Post by **pacsone** » Mon Sep 08, 2008 11:13 pm

For Linux/MacOS, please use the following command run from a local shell to check if both of the above executables are running:

Code: Select all

$ ps -ef|grep PacsOne

skreiner · Post by **skreiner** » Tue Sep 09, 2008 3:26 pm

OK,

Code: Select all

admin@ubuntu:/$ sudo ps -ef|grep PacsOne
admin    27172  6035  0 01:04 pts/0    00:00:00 grep PacsOne

Can you help me understand this?

Post by **pacsone** » Tue Sep 09, 2008 9:23 pm

This means PacsOne Server service was not even started.

Try running the following command to start it:

Code: Select all

# /etc/init.d/pacsone start

skreiner · Post by **skreiner** » Wed Sep 10, 2008 8:10 pm

OK, now:

admin@ubuntu:/$ sudo ps -ef|grep PacsOne
admin 6054 1 0 12:40 pts/0 00:00:00 /home/pacsone/PacsOneSrv.exe --pidfile=/home/pacsone/pacsone.pid
admin 6055 6054 0 12:40 pts/0 00:00:00 PacsOne.exe PacsOne
admin 6056 6054 0 12:40 pts/0 00:00:00 PacsOneHL7.exe PacsOne
admin 6401 5996 0 13:03 pts/0 00:00:00 grep PacsOne

but, unfortunately I can still not access PacsOne from the GE machine. I can DICOM ping from server to the GE device, but don't know how to do it the other way around. There is a button on the GE device that says "Verify" that is likely running the C-ECHO command but it returns an error telling me to check the configuration, which I have done multiple times. Also from the GE device I tried querying the IP address and appropriate port and AE title and get an error. Same things happen when I have it try to upload.

Also, how can I set it so that pacsone automatically loads every time the server starts? I don't want to have to verify that pacsone is running every time the server restarts.

Thank you for your help.

Post by **pacsone** » Wed Sep 10, 2008 8:32 pm

1. The PacsOne Server startup script under /etc/init.d/ should be run automatically every time you restart the server. If not, you should check with your Linux admin and find out if there is any security policy which may be preventing that script from being run.

2. Try to Dicom-ping (C-ECHO) from the GE device, then check the PacsOne Server logs under the log/${AeTitle} sub-folder where PacsOne is installed, and see if PacsOne has actually received the association request from the IP address where the GE device is located. If not, then either the IP address/TCP port settings on the GE device was mis-configured, or there is a firewall blocking the TCP port PacsOne Server was configured to listen to.

skreiner · Post by **skreiner** » Fri Oct 03, 2008 1:31 am

OK, I never quite got this to work. I am trying to figure out where the disconnect is. Now however, I can't seem to start PacsOne. I have tried /etc/init.d/pacsone start but it doesn't seem to start the program. I haven't changed anything. I can still access the sith through http://localhost/pacsone/home.php. What do you suspect is the problem now?

Post by **pacsone** » Fri Oct 03, 2008 4:38 am

Did you check the syslog (/var/log/messages) or the PacsOne Server logs under the log/ sub-folder where PacsOne is installed and see if there is any error logged?

skreiner · Post by **skreiner** » Fri Oct 03, 2008 2:20 pm

I don't see any errors in the messages file or in the log folder.

Post by **pacsone** » Fri Oct 03, 2008 2:54 pm

Then how did you tell PacsOne Server was not started?

skreiner · Post by **skreiner** » Fri Oct 03, 2008 8:38 pm

I typed ps -ef|grep PacsOne at the command line and it only returned the admin line.

Post by **pacsone** » Fri Oct 03, 2008 11:18 pm

Try stopping and restarting PacsOne Server, then run the following command from a local shell:

Code: Select all

# grep PACSONE /var/log/messages

Also, check the date/time of PacsOne Server log file for today under the log/${AeTitle}/ sub-folder where PacsOne is installed, and see if there is anything logged in today's log.