Error C004, can't c-move certain images

I have an issue sending some of the images from our Conquest server. It seems like images with a date newer than 2008 don't want to go anywhere, but older cases have no issues being pushed or pulled. It might not be specifically January 1st, 2008 that is the dividing line, it just seems that 2008 and newer generally don't transfer.

Other DICOM devices that query the Conquest server get "C004", and when I try to push from Conquest, I see the following:

Query Distinct Tables: DICOMImages, DICOMSeries, DICOMStudies

Columns : DICOMImages.SOPClassUI, DICOMImages.SOPInstanc, DICOMSeries.Modality, DICOMSeries.SeriesDesc, DICOMSeries.SeriesInst, DICOMSeries.SeriesNumb, DICOMStudies.StudyDate, DICOMStudies.PatientNam, DICOMStudies.PatientID, DICOMStudies.StudyInsta,DICOMImages.ObjectFile,DICOMImages.DeviceName

Where : DICOMStudies.StudyDate = '20080112' and DICOMStudies.PatientID = '81499' and DICOMSeries.StudyInsta = DICOMStudies.StudyInsta and DICOMImages.SeriesInst = DICOMSeries.SeriesInst

Order : (null)
Records = 3
Number of images to send: 3
MyPatientRootRetrieveGeneric :: RetrieveOn
Locating file:MAG2 81499\1.2.392.200036.9125.3.69122024135.64542514381.12929284_1001_001001_12628080750c27.dcm
Locating file:MAG2 81499\1.2.392.200036.9125.3.69122024135.64542514382.12929285_1002_001002_12628080770c28.dcm
Locating file:MAG2 81499\1.2.392.200036.9125.3.69122024135.64542514382.12929286_1003_001003_12628080790c29.dcm
Sending file : Y:\81499\1.2.392.200036.9125.3.69122024135.64542514381.12929284_1001_001001_12628080750c27.dcm
Image Loaded from Read Ahead Thread, returning TRUE
Retrieve: remote connection dropped after 0 images, 3 not sent
C-Move (PatientRoot)
UPACS THREAD 199766: ENDED AT: Mon May 17 12:37:42 2010
UPACS THREAD 199766: TOTAL RUNNING TIME: 4 SECONDS

I did a little testing, and it seems that the time period is from around the beginning of 2008 until april-ish 2009. There have been a couple instances where some of one modality will transfer from that day but other modalities won't, for example CT transfers but CR doesn't.

I've done yet more investigation, and it turns out that:

Status: a900 Status Information:-
Data Set does not match SOP Class (Failure)

This error is from another device that uses the dcmtk library that has the same images on it. The problem didn't originate on the conquest server, so, I may have to look elsewhere for a solution, but is there any way I can get around this problem with Conquest?

Just for the sake of completeness, I have discovered that, for some reason, the Study UIDs on the cases that cause this error end in a period, which of course is a Bad Thing(tm). Currently I am blaming it on the server I moved the images from (non-conquest). I'm going to write a script to use dcmtk's dcmodify command to generate new, clean Study UIDs.

Could I also use an importconverter to see if the last character is a period, and then append a couple tags to the UID to repair it?

I have written scripts that do this, using dcmtk, and it works, but I'd like to be able to just send images to conquest, and have it repair them if they are invalid.

I'd rather not generate new UIDs if the UID is valid, that will cause other issues - maybe I can use newuids only if the last character is a period?

Edit: It seems I can. This should work great - thanks Marcel.