Fix for 1.4.13 transfer problems

  • Hi,

    there have been several reports of communication problems with version 1.4.13. For example: failure to tranmit images, failure to echo, server closing due to memory allocation problems. This is probably due to one or more old bugs in the dicom library that are now exposed, because jpeg support is now by default enabled and with that the little endian explicit transfer syntax is switched on. This has been the case for several versions, but however it does not seem to work correctly in all circumstances - suggestions about the exact cicumstances are welcome.

    To fix these problems, please manually modify one line in file "DGATESOP.LST" as shown here, the change is in line 108:


    LittleEndianImplicit 1.2.840.10008.1.2 transferLittleEndianExplicit 1.2.840.10008.1.2.1 transfer#BigEndianExplicit 1.2.840.10008.1.2.2 transfer


    LittleEndianImplicit 1.2.840.10008.1.2 transfer
    #LittleEndianExplicit 1.2.840.10008.1.2.1 transfer
    #BigEndianExplicit 1.2.840.10008.1.2.2 transfer


  • Would this fix the errors I am getting here...

    [SRV1452] UPACS THREAD 37: STARTED AT: Fri Aug 15 12:20:04 2008
    [SRV1452] Calling Application Title : "1452CARM "
    [SRV1452] Called Application Title : "SRV1452 "
    [SRV1452] Application Context : "1.2.840.10008."
    [SRV1452] Presentation Context 0 "1.2.840.10008."
    [SRV1452] Presentation Context 1 "1.2.840.10008."
    [SRV1452] [recompress]: recompressed with mode = j3 (strip=0)
    [SRV1452] ***Refused to enter inconsistent link PatientID into DICOMStudies: PatientID = 'TOR 1000021' StudyInsta = '', Old='TOR 1000020', Refused='TOR 1000021'
    [SRV1452] ***Error saving to SQL: MONROY__MARIA\
    When the server window is closed there is also a database error pop up window...

    Database connection failed.
    ErrorMessage=Unspecified error
    Description=[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

    Any help would be great,



  • Hello,

    We run Conquest v14.12 on WinServer2003 with MSSQL2005 and I'm familiar to that Patient_ID inconsistentency error. It occures every time when you try to overwrite an existing study with the same study containing updated Patient_ID.
    I use to delete previous study and then import another updated one.

Participate now!

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