Error transferring to Conquest

We've had this error come up a couple times on different X-ray PC's when attempting to transfer to Conquest:

4/25/2016 12:04:26 PM DICOM problem: [CONQUEST] ***SQLITEExec error: column SOPInstanc is not unique
4/25/2016 12:04:26 PM DICOM problem: [CONQUEST] ***Error saving to SQL: 15072\1.2.276.0.54.10.2.20160104161134.51.661845_0001_000001_1461603866001c.dcm

These errors come up on completely different patients and studies. For instance, here's another one:

4/22/2016 9:37:15 AM DICOM problem: [CONQUEST] ***SQLITEExec error: column SOPInstanc is not unique
4/22/2016 9:37:15 AM DICOM problem: [CONQUEST] ***Error saving to SQL: 51446\1.2.276.0.54.10.2.20160113134959.818.179571_0001_000003_146133583500a7.dcm

Anyone have an idea what causes this and what I can do to fix it? I did attempt to re-generate the database with no success.

I'm running version 1.4.17d on Windows Server 2012 R2. I've found the SOPInstanceUID, but how do I query it against the Conquest server?

Quote from marcelvanherk

Hi,

go to the query move page. Double click on label "Series Number", enter the SopInstanceUID into "Image UID", and select Query level "Image".

regards,

Marcel

Display More

Thanks Marcel. I did as you instructed and I did indeed find the SopInstanceUID on another image for a different patient. I removed the image and re-sent from the X-Ray PC and it transmitted successfully. It seems odd to me that somehow we got a duplicate, but our CR software is known to have some quirks.

I was discussing the error with someone who knows much more about these things, and he suggested that perhaps the issue was caused by the person doing the x-ray doing it under the last patient to have been imaged, so I investigated. He was correct, however it was in reverse. A patient had been done after this one that got an error, only their images got sent first, so when these got sent, they got the error.

This is the image info from the image that was already on the server with the conflicting SOPInstanceUID:

08/05 Specific Character Set ISO_IR 100
08/08 Image Type ORIGINAL\PRIMARY
08/16 SOP Class UID 1.2.840.10008.5.1.4.1.1.1
08/18 SOP Instance UID 1.2.276.0.54.10.3.20160104161134.564.401848
08/20 Study Date 20160413
08/23 Image Date 20160413
08/30 Study Time 094306
08/33 Image Time 094939

And here's the info from the one that got the error:

08/05 Specific Character Set ISO_IR 100
08/08 Image Type ORIGINAL\PRIMARY
08/16 SOP Class UID 1.2.840.10008.5.1.4.1.1.1
08/18 SOP Instance UID 1.2.276.0.54.10.3.20160104161134.564.401848
08/20 Study Date 20160412
08/23 Image Date 20160412
08/30 Study Time 114515
08/33 Image Time 115024

So, turns out to be a workflow error in the end.