The following is some steps you can take to help troubleshoot issues with Conquest receiving files. These are the steps I have followed to fix specific problems I have encountered. This may fix your problem, this may make your problem worse. Proceed with caution.

Steps to take when Conquest logs:

***Error saving to SQL:

 Turn on Debug Log (more information) on the Conquest console.

 Next time the event occurs (within 5 minutes usually) you may get a message similar to:

***Failed SQLExecDirect : INSERT INTO DICOMImages (SOPInstanc, SOPClassUI, ImageNumbe, ImageDate, ImageTime, SamplesPer, PhotoMetri, Rows, Colums, BitsStored,ImageType, ImagePat, SeriesInst, AccessTime, ObjectFile, DeviceName) VALUES (’1.2.840.113619.2.116.4835844.1159511528.0.9207.4′, ‘1.2.840.10008.5.1.4.1.1.6.1′, ‘0001′, ‘20060929′, ‘123331′, ‘1′, ‘MONOCHROME2′, ‘480′, ‘640′, ‘8′, ‘ORIGINAL\PRIMARY\GYNECOLOGY\0001\GEMSSINGLEFRAME\GEMSMGCOUNT1′, ‘999999999′, ‘1.2.840.113619.2.116.4835844.1159511528.0.9214′, 1159887872, ‘999999999\1.2.840.113619.2.116.4835844.1159511528.0.9213\1.2.840.113619.2.116.4835844.1159511528.0.9214\1.2.840.113619.2.116.4835844.1159511528.0.9207.4.v2′, ‘MAG0′)

03/10/2006 9:04:48 AM [CDPACSBU1] ***Error: 2627: 23000: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint

‘PK__DICOMImages__0425A276′. Cannot insert duplicate key in object ‘dbo.DICOMImages’.

03/10/2006 9:04:48 AM [CDPACSBU1] ***Unable to DB.Add()

03/10/2006 9:04:48 AM [CDPACSBU1] ***SQL: INSERT INTO DICOMImages (SOPInstanc, SOPClassUI, ImageNumbe, ImageDate, ImageTime, SamplesPer, PhotoMetri, Rows, Colums, BitsStored, ImageType, ImagePat, SeriesInst, AccessTime, ObjectFile, DeviceName) VALUES (’1.2.840.113619.2.116.4835844.1159511528.0.9207.4′,

‘1.2.840.10008.5.1.4.1.1.6.1′, ‘0001′, ‘20060929′, ‘123331′, ‘1′, ‘MONOCHROME2′, ‘480′, ‘640′, ‘8′, ‘ORIGINAL\PRIMARY\GYNECOLOGY\0001\GEMSSINGLEFRAME\GEMSMGCOUNT1′, ‘999999999′, ‘1.2.840.113619.2.116.4835844.1159511528.0.9214′, 1159887872, ‘999999999\1.2.840.113619.2.116.4835844.1159511528.0.9213\1.2.840.113619.2.116.4835844.1159511528.0.9214\1.2.840.113619.2.116.4835844.1159511528.0.9207.4.v2′, ‘MAG0′)

03/10/2006 9:04:48 AM [CDPACSBU1] ***Error: 2627: 23000: [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint ‘PK__DICOMImages__0425A276′. Cannot insert duplicate key in object ‘dbo.DICOMImages’.

03/10/2006 9:04:48 AM [CDPACSBU1] ***Error saving to SQL: 999999999\1.2.840.113619.2.116.4835844.1159511528.0.9213\1.2.840.113619.2.116.4835844.1159511528.0.9214\1.2.840.113619.2.116.4835844.1159511528.0.9207.4.v2

This means that the receiving Conquest already has an entry for this file in its DATABASE. The important line is: “Cannot insert duplicate key in object

‘dbo.DICOMImages’”. There may other versions of this message, which may be similar or vastly different. The following steps are only to be used as a guide.

To see the files in question, goto the path indicated by “999999999\1.2.840.113619.2.116.4835844.1159511528.0.9213\1.2.840.113619.2.116.4835844.1159511528.0.9214\1.2.840.113619.2.116.4835844.1159511528.0.9207.4.v2″, (without including the file name).

Copy into the clipboard the “SOPInstanc” number, which is identified by the line:

***SQL: INSERT INTO DICOMImages (SOPInstanc, SOPClassUI, ImageNumbe, ImageDate, ImageTime, SamplesPer, PhotoMetri, Rows, Colums, BitsStored, ImageType, ImagePat, SeriesInst, AccessTime, ObjectFile, DeviceName) VALUES (’1.2.840.113619.2.116.4835844.1159511528.0.9207.4′,’1.2.840.10008.5.1.4.1.1.6.1′

This is telling you that SOPInstanc is the first value, SOPClassUI is the second, etc. The values follow next, in our case we want

“1.2.840.113619.2.116.4835844.1159511528.0.9207.4″

On the receiving system (where the error message occured), open Microsoft SQL Server Management Studio Express (or equivelent tool).

Navigate to the DATABASE in question, and the click on New Query.

Type the following, replacing NNN with the SOPINSTANC # that you copied previously.

SELECT     DICOMIMAGES.*

FROM         DICOMIMAGES

WHERE SOPINSTANC = ‘NNN’

Then press EXECUTE

In the results pane, you should get one entry. One of the columns will be OBJECTFILE. This is the file that the receiving Conquest system has that it thinks is identical to the file it is refusing to receive. Right click on it and COPY.

Open the folder containing the file in the previous step (may help to PASTE the path from your previous COPY).

Copy this file into another location where you can work on it without risking any data loss.

If this file is compressed it must be uncompressed.  To uncompress the file with Conquest run the following command from inside the Conquest directory:

dgate -NDC:\location of file\filename.EXT

You can now use a program like DicomWorks to view this file and perhaps the dicom tags of the file.

If the file you are looking at is the same as the file that is being sent to Conquest, you may be able to simply remove the file from the receiving Conquest system, which will allow the new file to be written. 

C:\pacs>dgate –deleteimagefile:c:\pacs\data\not-needed-file.ext

If the file needs to be kept, a new SOPInstanc tag needs to be entered using DicomWorks that is unique and does not already exists on the server. This should be done on all images from the study in question.

Copy all image files from the study into a temporary working folder. Tell Conquest to delete the study.

Dgate –deletestudy:studyuid

To get a unique tag, send a test study from a modality, open it in DicomWorks to get the SOPINSTNC string, record the string, and then delete the test study.  Now enter the SOPINSTNC string into the study in question and drag and drop the files onto Conquest.

Bookmark to: