ERROR: Received RSP with Status 0110H

[Joey]

My application uses several dcm4che toolkit utils to send scans to a target pacs.

Sending scans to my local dcm4chee pacs works fine.

The same exact application is also deployed on a production server together with a dcm4chee pacs.

the part where the application tries to send the scan to the pacs I receive the following error:

Scanning files to send                                                          
.                                                                              
Scanned 1 files in 0.098s (=98ms/file)                                          
14:31:16,053 INFO   - Association(1) initiated Socket[addr=/127.0.0.1,port=11112,localport=56768]
14:31:16,055 INFO   - DCM4CHEE(1): A-ASSOCIATE-RQ DCM4CHEE << DCMSND            
14:31:16,061 INFO   - DCM4CHEE(1): A-ASSOCIATE-AC DCMSND >> DCM4CHEE            
Connected to DCM4...@127.0.0.1:11112 in 0.055s                                
14:31:16,134 INFO   - DCM4CHEE(1) << 1:C-STORE-RQ[pcid=3, prior=0              
    cuid=1.2.840.10008.5.1.4.1.1.2/CT Image Storage                            
    iuid=1.2.840.113704.1.111.3352.1107859681.1270                              
    ts=1.2.840.10008.1.2.4.91/JPEG 2000 Image Compression]                      
14:31:16,470 INFO   - DCM4CHEE(1) >> 1:C-STORE-RSP[pcid=3, status=110H          
    error=org.dcm4che.net.DcmServiceException: javax.ejb.CreateException:      
    cuid=1.2.840.10008.5.1.4.1.1.2/CT Image Storage                            
    iuid=1.2.840.113704.1.111.3352.1107859681.1270]                            
F                                                                              
Sent 0 objects (=0.0KB) in 0.449s (=0.0KB/s)                                    
14:31:16,511 INFO   - DCM4CHEE(1) << A-RELEASE-RQ                              
14:31:16,512 INFO   - DCM4CHEE(1) >> A-RELEASE-RP                              
Released connection to DCM4CHEE@127.0.0.1:11112                                
14:31:16,512 INFO   - DCM4CHEE(1): close Socket[addr=/127.0.0.1,port=11112,localport=56768]
                                                                               
null                                                                            
ERROR: Received RSP with Status 0110H for /var/services/homes/user/foo/dicom/quarantine/a7fb486ecc6250b3b9736487f0ddcefd, cuid=1.2.840.10008.5.1.4.1.1.2     , tsuid=1.2.840.10008.1.2.4.91
(0000,0002) UI #26 [1.2.840.10008.5.1.4.1.1.2] Affected SOP Class UID          
(0000,0100) US #2 [32769] Command Field                                        
(0000,0120) US #2 [1] Message ID Being Responded To                            
(0000,0800) US #2 [257] Command Data Set Type                                  
(0000,0900) US #2 [272] Status                                                  
(0000,0902) LO #64 [org.dcm4che.net.DcmServiceException: javax.ejb.CreateException:] Error Comment
(0000,1000) UI #42 [1.2.840.113704.1.111.3352.1107859681.1270] Affected SOP Instance UID

I am not exactly sure what this error implies, I could not find clear information on this.

However I can disclose the following:

1. It is the exact same dicom file that was used locally. and it seems to happen with all dicom files I have on the production server.
   
2. The application replaces the known Patient ID (0010, 0020) in the file by a custom Patient ID

Thanks

[Joey]

Manually using dcmsnd on a unaltered dicom file renders the same error.

Might this be a configuration, or a database issue?

[fleetwoodfc]

The dcm4chee server  server.log file should provide detail of what caused the java exception. 

[Joey]

Thanks fleetwood,

I am not sure what caused this change in configuration, but I followed your advice inspecting the server.log file.

I found lines saying something in the direction of "acces denied for root @ localhost".

I then proceeded to do the following:

1. Stopped the dcm4chee service.
   
2. Stopped the phpmyadmin service.
   
3. Reset the root password via mariadb.
   
4. Stopped mariadb.
   
5. Started mariadb.
   
6. Started phpmyadmin.
   
7. Started dcm4chee.
   
8. Checked if I could log in all the web interfaces, which worked.
   
9. Ran my application again, and no errors this time, the dcm4chee pacs receives the files.
   

So in the end it seems to have been a database access issue, but I am not exactly how this happened.

[Salinda Karunarathna]

Exact same problem for me. Created database via 'sa' and resolved the problem. 
Thanks for the hint.