Error Receiving Images from another Server

    on 1.4.19d and receiving the error below when trying to receive forwarded messages. I had to check the enable Jpeg as had more errors initially. I am on SQL Server 2014 and I have ammended the database to collect more dicom tags, tested that before the forward and was working fine.

    Code
    [CONQUESTSRVIMGDW] UPACS THREAD 7: STARTED AT: Thu Jan 31 14:27:20 2019

    [CONQUESTSRVIMGDW]  Calling Application Title : "CZMA            "

    [CONQUESTSRVIMGDW]  Called Application Title : "CONQUESTSRVIMGDW"

    [CONQUESTSRVIMGDW]  Application Context : "1.2.840.10008.3.1.1.1", PDU length: 16384

    [CONQUESTSRVIMGDW]  Presentation Context 0 "1.2.840.10008.5.1.4.1.1.66" 1

    [CONQUESTSRVIMGDW] ***Error saving to SQL: 1276689\1.2.276.0.75.2.2.42.50123836188.20190131143702407.4748628530_0001_000000_15489448400005.dcm

    [CONQUESTSRVIMGDW] UPACS THREAD 7: ENDED AT: Thu Jan 31 14:27:20 2019

    [CONQUESTSRVIMGDW] UPACS THREAD 7: TOTAL RUNNING TIME: 0 SECONDS

    Thanks. That gives me more info. I have set the TruncateFieldNames = 50, and my database now have most of the fiieldnames as I want them but it seems something is not right when saving new files. Any ideas on anything else I need to configure?




    Code
    [CONQUESTSRVIMGDW] ***SQL: INSERT INTO DICOMImages (SOPInstanc, SOPClassUI, ImageNumbe, ImageDate, ImageTime, ImagePat, SeriesInst, AccessTime, ObjectFile, DeviceName) VALUES ('1.2.276.0.75.2.2.42.50123836188.20190131150547717.4748501400', '1.2.840.10008.5.1.4.1.1.66', '0', '20190131', '150547.000', '2545413', '1.2.276.0.75.2.2.42.50123836188.20190131150547733.4748971530', 1548946560, '2545413\1.2.276.0.75.2.2.42.50123836188.20190131150547733.4748971530_0001_000000_15489465650032.dcm', 'MAG0')

    [CONQUESTSRVIMGDW] ***Error: 207: S0022: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'SOPInstanc'.

    Found the issue 'sort of', the server was running in services as I changed dicom.ini. Closing conquest and the service seem to have resolved the issue although I still have an issue when browsing the database as the where clause still retains the old fieldname

Participate now!

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

Register Yourself Login