Conquest DICOM server 1.5.0(b) released

  • Hello. New US system - new problem. Hospital got new US system Philips UPIQ7. The problem is that studies got"***Error saving to SQL". What can it be? Thanks.


    [CONQUESTSRV67] Calling Application Title : "EPIQ7 77 [CONQUESTSRV67] Called Application Title : "CONQUESTSRV67 [CONQUESTSRV67] Application Context : "1.2.840.10008.", PDU Iength: 32768 [CONQUESTSRV67] Presentation Context 8 "1.2.840.18008." 1 [CONQUESTSRV67] Presentation Context 1 "1.2.840.10008." 1 [CONQUESTSRV67] Presentation Context 2 ""e [CONQUESTSRV67] Presentation Context 3 "1.2.840.10008. 1 [CONQUESTSRV67] Presentation Context 4 "1.2.840.10008." 1 [CONQUESTSRV67Ị Presentation Context 5 "1.2.840.10008. 1 [CONQUESTSRV67] Presentation Context 6 "1.2.840.10008.1.2e.1 0 [CONQUESTSRV67] Presentation Context 7 "1.2.84e.10008.1.1" 1 [CONQUESTSRV67] Presentation Context 8 "1.2.840.10008.* 1 [CONQUESTSRV67] Presentation Context 9 "1.2.840.10008." 1 [CONQUESTSRV67] Presentation Context 10 "1.2.840.10008." 1 [CONQUESTSRV67] Presentation Context 11 "1.2.840.10008." 1 [CONQUESTSRV67] Presentation Context 12 "1.2.840. 10008." 1 [CONQUESTSRV67] Presentation Context 13 "1.2.840.19008." 1 [CONQUESTSRV67] Presentation Context 14 "1.2.840.10008." 1 [CONQUESTSRV67] Presentation Context 15 "1.2.840.10008." 1 [CONQUESTSRV67] Presentation Context 16 "1.2.840.10008." 1 [CONQUESTSRV67] Presentation Context 17 "1.2.840.10008." 1 [CONQUESTSRV67] Presentation Context 18 "1.2.840.10008." 1 E [CONQUESTSRV67] Presentation Context 19 "1.2.840.10008." 1 [CONQUESTSRV67] Presentation Context 20 "1.2.840.10008." 1 [CONQUESTSRV67] ***Error saving to SQL: TEST1\1.2.840.113663.1500.1.489861291.2.1.20220222.11233.5 001 000001 164544835382c3.dcm [CONQUESTSRV67] UPACS THREAD 830: ENDED AT: Mon Feb 21 15:59:13 2022 [CONQUESTSRVV67] UPACS THREAD 830: TOTAL RUNNING TIME: 13 SECONDS

  • Dear Marcel,

    maybe it's not bad to write my case here (this topic). Today i'm trying to connect newest Philips Diagnost C90 and we can't go through association test. When I turn on debug lvl 2, i get logs just like below:

    Connected by address: 030110ac

    Testing transfer: '1.2.840.10008.1.2.1' against list #0 = '1.2.840.10008.1.2'

    Testing transfer: '1.2.840.10008.1.2.1' against list #1 = '1.2.840.10008.1.2.1'

    Testing transfer: '1.2.840.10008.1.2.1' against list #0 = '1.2.840.10008.1.2'

    Testing transfer: '1.2.840.10008.1.2.1' against list #1 = '1.2.840.10008.1.2.1'

    Testing transfer: '1.2.840.10008.1.2.1' against list #0 = '1.2.840.10008.1.2'

    Testing transfer: '1.2.840.10008.1.2.1' against list #1 = '1.2.840.10008.1.2.1'

    Arena 0:

    system bytes = 1138688

    in use bytes = 986416

    Arena 1:

    system bytes = 442368

    in use bytes = 421760

    Total (incl. mmap):

    system bytes = 1716224

    in use bytes = 1543344

    max mmap regions = 2

    max mmap bytes = 446464

    UPACS THREAD 2: STARTED AT: Wed May 25 13:59:38 2022

    *** connection terminated

    UPACS THREAD 2: ENDED AT: Wed May 25 13:59:38 2022


    I've updated dgate.lst (to latest from github. Could You Marcel point me some solution here please, i'll be very grateful fo help.

  • Hm,

    not sure what is going on. I would expect it sends a regular C-ECHO, but apparantly it does not. Dgatesop.lst is correct, and should allow all requests. I think you need to run a packet sniffer to see what the scanner is trying to do.


  • Dedicated DICOM Ping from Philips system gives logs without errors.


    Hah, when i leave on machine just SCU/SCP Transfer ExpliciLittleEndian with available SCU/SCP CR/DX Storage/Processing SOP Classes, the communication works with real images transfer. however the Dicom association test still gives termination and i suppose that it may be some newest features checking for integration with philips vna systems. For now, i let it just work and monitor the logs. Thank You Marcel for time!

  • i am sorry, explain me please what its mean.

    root@ctvm:/home/dicom/conquest_mini150c# ./dgate -v -r

    Regen Database

    Step 1: Re-intialize SQL Tables

    Dropping Existing tables (if-any)

    Worklist is empty

    Dropping worklist

    Dropping other tables

    WorkList Database

    Patient Database

    Study Database

    Series Database

    ***Failed MYSQLExec : CREATE INDEX idx_studyinsta_seriesinst ON DICOMSeries (PatientID, StudyInsta)

    ***Error: Key column 'PatientID' doesn't exist in table

    Image Database

    ***Failed MYSQLExec : CREATE INDEX idx_seriesinst_sopinstanc ON DICOMImages (StudyInsta, SeriesInst)

    ***Error: Key column 'StudyInsta' doesn't exist in table

    Step 2: Load / Add DICOM Object files

    Regen Device 'MAG0'

    I am found. |But i am use mariadb

    N30) The following indices are needed to speed up performance on postgres - installed by test database in 1.5.0c

    CREATE INDEX idx_patientid ON dicomstudies(patientid);

    CREATE INDEX idx_patientid_studyinsta ON dicomstudies(patientid, studyinsta);

    CREATE INDEX idx_studyinsta_seriesinst ON dicomseries(studyinsta,seriesinst);

    CREATE INDEX idx_seriesinst_sopinstanc ON dicomimages(seriesinst, sopinstanc); Also in dgate 1.5.0c

  • Yes, I downloaded it 2 weeks ago, now I could not compile the last code from the git because of this error. (dgate.cpp)

    Please, if possible, release a stable release. 1.5.0с

  • Hm,

    there must be mistake. These issues exists in 1.5.0b, but were fixed. I am happy to generate a stable release 1.5.0c but it is a lot of work, in particular updating documentation etc. Please use the latest code on github as is.


Participate now!

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