Error: Unable to write DICOM object

Trouble during PacsOne Server installations
Post Reply
ncite
Posts:25
Joined:Tue Jun 01, 2010 5:07 pm
Error: Unable to write DICOM object

Post by ncite » Thu Sep 23, 2010 1:00 pm

We have Pacsone 6.1.1. We send and retrieve images with efilm. Sending the images has no problems. When we retieve certain images we get Error: Unable to write DICOM object (Study Root Retrieve).

When I look on the pacs server all the images are there and I can view them. I can ping from pacs to the efilm stations just fine and efilm verifies the pacs server.

This is the message I get in the logs.
Thu Sep 23 10:49:54 2010 INFO - C-STORE Sub-session: <30> started for SCP: 172.20.1.144 Port: 4006
Thu Sep 23 10:49:54 2010 INFO - <30> Sending A-ASSOCIATE-RQ PDU
Thu Sep 23 10:49:54 2010 INFO - <30> Waiting for A-ASSOCIATE result
Thu Sep 23 10:49:55 2010 INFO - <30> A-ASSOCIATE-RQ accepted
Thu Sep 23 10:49:55 2010 INFO - <30> Sending P-DATA-TF PDU
Thu Sep 23 10:49:56 2010 INFO - 76 tags processed in CDataSetPdv
Thu Sep 23 10:50:56 2010 ERROR - Session: <30> timed out for client: 172.20.1.144, aborting
Thu Sep 23 10:50:56 2010 INFO - Session: <30> disconnected for client: 172.20.1.144
Thu Sep 23 10:51:42 2010 ERROR - Session: <28> timed out for client: 172.20.1.54, aborting
Thu Sep 23 10:51:42 2010 INFO - Session: <28> disconnected for client: 172.20.1.54
Thu Sep 23 10:51:42 2010 INFO - <22> A-ASSOCIATE-RELEASE-RQ PDU received
Thu Sep 23 10:51:42 2010 INFO - <22> Sending A-ASSOCIATE-RELEASE-RSP PDU
Thu Sep 23 10:51:42 2010 INFO - <22> A-ASSOCIATE-RELEASE-RSP PDU sent successfully
Thu Sep 23 10:51:42 2010 INFO - Session: <22> disconnected for client: 172.20.1.54
Thu Sep 23 10:51:56 2010 ERROR - Session: <29> timed out for client: 172.20.1.144, aborting
Thu Sep 23 10:51:56 2010 INFO - Session: <29> disconnected for client: 172.20.1.144

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Thu Sep 23, 2010 3:28 pm

The error logged by PacsOne Server suggests that it has timed out after waiting 60 seconds for the response back from eFilm for the 1st dataset sent, so you should check with eFilm support and see why it's not responding to the C-STORE-RQ sent from PacsOne.

There seem to be multiple sessions active with this eFilm, so you should also check and make sure your version of eFilm can handle multiple simultaneous connections.

ncite
Posts:25
Joined:Tue Jun 01, 2010 5:07 pm

Post by ncite » Thu Sep 23, 2010 3:41 pm

I dont know if this has anything to do with it or not. This all started after the hard drive that the images get store to became full. I went under the configuration in pacs and changed the short-term archive directory to a new drive.

Could that be causing any issues? Did I change the right directory path?

ncite
Posts:25
Joined:Tue Jun 01, 2010 5:07 pm

Post by ncite » Thu Sep 23, 2010 8:58 pm

It looks like they can send and recieve any thing thats on the new achrive drive. But any thing on the old one isn't being pulled up. When I look in pacs it show the image and location but no other information about the images.

Will doing a database integrity check help this problem?

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Thu Sep 23, 2010 9:20 pm

As long as you don't remove the old drive, all the Dicom images stored there should still be accessible to PacsOne Server.

To verify this, you can find any old study that's stored on the old drive, navigate through to the Image Thumbnails page, then click on the URL link underneath any of the thumbnail images, which will display the full path to where the raw Dicom image is stored on the old drive. Check and make sure the path is correct and there's no error being reported from that page.

Post Reply