Generic Error

  • I have about 7 Conquest workstations running and they are all auto forwarding studies without an problem.


    I needed to change destinations on one of those stations and after I have done so when I send to a GE Radworks workstation I get a generic error in the receive log and the patient is not received.


    This station was forwarding studies with out a problem before that and all i did was change the Dicom.ini file with the new Ae Title.



    What I have done thus far - deleted the entire folder containing conquest along with the service. Reinstalled v1413 from scratch with a new AE title. Same thing happens. Tried it to 2 different Radworks workstations with the same result. tried copying the auto forward portion of the Dicom.ini from a working station.


    Downloaded 1414 beta and extracted dgate & conquestdicomserver and updated them. All with the same result.


    If I do a query I can copy the patient without a problem, or I can pick it from the database and send it also without a problem. Seems it is only on the auto forward.


    Here is the path
    C:\CDS\_Dicom
    which has not been an issue in the past


    Code
    # Setup conquest server to forward all images received to a single modality andForwardAssociationLevel = *ForwardAssociationCloseDelay = 5ForwardAssociationRefreshDelay = 3600ExportConverters = 2ExportConverter0 = forward to AE_RAD1ForwardCollectDelay = 600MaximumExportRetries = 0MaximumDelayedFetchForwardRetries = 0



    Code
    A1SRQ 127.0.0.1 104 un
    V* * 1234 un
    S* * 5678 un
    AE_RAD1 192.168.2.22 3140 un
    AE_RADWORKS246 192.168.1.246 3140 un
    A1CC 192.168.30.74 104 un
    rdw_cape 192.168.1.38 104 un


    Any help would be greatly appreciated. It is driving me crazy!

  • The 2 destinations I have tried - one is odd and one is even length AE Ttitle.


    I have now tried a fresh install on another computer and still get the same results.


    Does anyone see anything wrong with the auto forwarding addition to the Dicom.ini? It's the only thing I can think of.


    manually sending it one series at a time works almost every time, and manually sending it works quite a lot but not always.

  • Hi,


    An attempt: you have exportconverters at 2, but that should not be an issue. Move the V* and S* lines to be the last in the file. Also try: "list known dicom providers" to see that there is no syntax error in acrnema.map


    Marcel

  • ok changed the export to 1 and moved the v and s lines of the acrnema.map file to the end


    This also happens and with this one file coinsides with the getting the generic errors


    Code
    [A1SRQ] ***Refused to enter inconsistent link SeriesInst into DICOMImages: PatientID = 'SRQ255676' SOPInstanc = '1.2.392.200036.9123.100.12.10..2008080514584.2' AND ImagePat = 'SRQ255676', Old='1.2.392.200036.9123.100.12.10..2008080514575.3.3', Refused='1.2.392.200036.9123.100.12.10..2008080514584.4.3'
    [A1SRQ] ***Error saving to SQL: SRQ255676\1.2.392.200036.9123.100.12.10..2008080514575.3.3_0004_000044_1217962957002b.v2


    These are part of the same exam and causes the MRI to lock up when sending when one of these comes up as well. Is there a setting I can change in the dicom.sql that will let it pass this by?


    We have the MRI service guys coming out to look at the software side of the MRI as well. But its baffling.


    Thanks for you assistance.

  • Hi,


    the error you show comes from incorrect DICOM data - re-using the same UID in a different patient or study. See sticky "why not to modify patient ID". Were these always the errors you got?


    Marcel

  • it's strange as it will show up in the middle of a study. Not sure what the MRI is doing to cause this part of it.


    This error does not shows up from time to time and I have seen it across all our Hitachi Aris 1s at some point. But this one site has this plus the generic error with no error on the conquest server.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!