Conquest stopped receiving

  • On27th we had issues with conquest, not receiving studies. The log shows the following error and I have attached my dicom.ini for your review. I restarted the services, now it's working fine.

    We need to avoid this error and make sure conquest runs fine all the time. Are we missing any configuration here?


    12/27/2021 3:51:19 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:19 PM***Error Connecting to SQL
    12/27/2021 3:51:21 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:21 PM ***Error Connecting to SQL
    12/27/2021 3:51:22 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:22 PM ***Error Connecting to SQL
    12/27/2021 3:51:24 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:24 PM ***Error Connecting to SQL
    12/27/2021 3:51:26 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:26 PM***Error Connecting to SQL
    12/27/2021 3:51:28 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:28 PM ***Error Connecting to SQL
    12/27/2021 3:51:29 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:29 PM ***Error Connecting to SQL
    12/27/2021 3:51:31 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:31 PM ***Error Connecting to SQL
    12/27/2021 3:51:33 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:33 PM ***Error Connecting to SQL
    12/27/2021 3:51:34 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:35 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:35 PM ***Error Connecting to SQL
    12/27/2021 3:51:35 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:35 PM ***Error connecting datasource:conquest user:conquest password:conquest
    12/27/2021 3:51:36 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:36 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:36 PM ***Error connecting datasource:conquest user:conquest password:conquest

    12/27/2021 3:51:36 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:36 PM***Error Connecting to SQL
    12/27/2021 3:51:37 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:37 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:38 PM *** FATAL: remaining connection slots are reserved for non-replication superuser connections
    12/27/2021 3:51:38 PM ***Error connecting datasource:conquest user:conquest password:conquest



    dicom.ini


    # This file contains configuration information for the DICOM server

    # Do not edit unless you know what you are doing


    [sscscp]

    MicroPACS = sscscp


    # Network configuration: server name and TCP/IP port#

    MyACRNema = AETITLE

    TCPPort = 104


    # Host, database, username and password for database

    SQLHost = 127.0.0.1

    SQLServer = conquest

    Username = conquest

    Password = conquest

    Postgres = 1

    DoubleBackSlashToDB = 1

    UseEscapeStringConstants = 1


    # Configure server

    ImportExportDragAndDrop = 1

    KeepAlive = 60

    ZipTime = 05:

    UIDPrefix = 1.2.826.0.1.3680043.2.135.738139.36139563

    EnableComputedFields = 1


    FileNameSyntax = 4


    # Configuration of compression for incoming images and archival

    DroppedFileCompression = un

    IncomingCompression = un

    ArchiveCompression = as


    # For debug information

    PACSName = PACSSERVER

    OperatorConsole = 127.0.0.1

    DebugLevel = 4


    # Configuration of disk(s) to store images

    MAGDeviceFullThreshHold = 30

    MAGDevices = 1

    MAGDevice0 = c:\dicom\

    NightlyCleanThreshhold = 1000


    # Configuration of forwarding and/or converter programs to export DICOM slices

    ForwardAssociationLevel = IMAGE

    ForwardAssociationCloseDelay = 5

    ForwardAssociationRefreshDelay = 3600

    ForwardAssociationRelease = 1


    ExportConverters = 1

    ExportConverter0 = forward to AE_TITLE


    ForwardCollectDelay = 60

    MaximumExportRetries = 0

    MaximumDelayedFetchForwardRetries = 0




  • Today found this error, can you check


    12/29/2021 10:43:29 AM [PACSSERVER] Connected by address: 15022e0a

    12/29/2021 10:43:29 AM [PACSSERVER] Testing transfer: '1.2.840.10008.1.2.4.50' against list #0 = '1.2.840.10008.1.2'

    12/29/2021 10:43:29 AM [PACSSERVER] Testing transfer: '1.2.840.10008.1.2.4.50' against list #1 = '1.2.840.10008.1.2.1'

    12/29/2021 10:43:29 AM [PACSSERVER] Testing transfer: '1.2.840.10008.1.2.4.50' against list #2 = '1.2.840.10008.1.2.4.57'

    12/29/2021 10:43:29 AM [PACSSERVER] ***No valid presentation contexts/transfer syntax found in 1 candidates

    12/29/2021 10:43:29 AM [PACSSERVER] ***In 1 presentation contexts

    12/29/2021 10:43:29 AM [PACSSERVER] *#Possible transfer syntaxes: 3

    12/29/2021 10:43:29 AM [PACSSERVER] no transfer syntax could be negotiated

    12/29/2021 10:43:29 AM [PACSSERVER] * multiplex: connection terminated

    12/29/2021 10:43:29 AM [PACSSERVER] Connected by address: 15022e0a

    12/29/2021 10:43:29 AM [PACSSERVER] Testing transfer: '1.2.840.10008.1.2.4.50' against list #0 = '1.2.840.10008.1.2'

    12/29/2021 10:43:29 AM [PACSSERVER] Testing transfer: '1.2.840.10008.1.2.4.50' against list #1 = '1.2.840.10008.1.2.1'

    12/29/2021 10:43:29 AM [PACSSERVER] Testing transfer: '1.2.840.10008.1.2.4.50' against list #2 = '1.2.840.10008.1.2.4.57'

    12/29/2021 10:43:29 AM [PACSSERVER] ***No valid presentation contexts/transfer syntax found in 1 candidates

    12/29/2021 10:43:29 AM [PACSSERVER] ***In 1 presentation contexts

    12/29/2021 10:43:29 AM [PACSSERVER] *#Possible transfer syntaxes: 3

    12/29/2021 10:43:29 AM [PACSSERVER] no transfer syntax could be negotiated

    12/29/2021 10:43:29 AM [PACSSERVER] * multiplex: connection terminated

    12/29/2021 10:43:41 AM [PACSSERVER] Connected by address: 0100007f

    12/29/2021 10:43:41 AM [PACSSERVER] Testing transfer: '1.2.840.10008.1.2' against list #0 = '1.2.840.10008.1.2'

    12/29/2021 10:43:41 AM [PACSSERVER] 0000,0002 18 UI AffectedSOPClassUID "1.2.840.10008.1.1"

    12/29/2021 10:43:41 AM [PACSSERVER] 0000,0100 2 US CommandField 48

    12/29/2021 10:43:41 AM [PACSSERVER] 0000,0110 2 US MessageID 7

    12/29/2021 10:43:41 AM [PACSSERVER] 0000,0800 2 US DataSetType 257

    12/29/2021 10:43:41 AM [PACSSERVER] 0002,0010 17 UI TransferSyntaxUID "1.2.840.10008.1.2"

    12/29/2021 10:43:41 AM [PACSSERVER] 9999,0400 6 LO ConquestConsoleComma "silent"

    12/29/2021 10:43:43 AM [PACSSERVER] Connected by address: 15022e0a

    12/29/2021 10:43:43 AM [PACSSERVER] Testing transfer: '1.2.840.10008.1.2.4.50' against list #0 = '1.2.840.10008.1.2'

    12/29/2021 10:43:43 AM [PACSSERVER] Testing transfer: '1.2.840.10008.1.2.4.50' against list #1 = '1.2.840.10008.1.2.1'

    12/29/2021 10:43:43 AM [PACSSERVER] Testing transfer: '1.2.840.10008.1.2.4.50' against list #2 = '1.2.840.10008.1.2.4.57'

    12/29/2021 10:43:43 AM [PACSSERVER] ***No valid presentation contexts/transfer syntax found in 1 candidates

    12/29/2021 10:43:43 AM [PACSSERVER] ***In 1 presentation contexts

    12/29/2021 10:43:43 AM [PACSSERVER] *#Possible transfer syntaxes: 3

    12/29/2021 10:43:43 AM [PACSSERVER] no transfer syntax could be negotiated

    12/29/2021 10:43:43 AM [PACSSERVER] * multiplex: connection terminated

  • the sender is sending huge no of studies continuously on daily basis, conquest stops in-between,


    is there a way to control inbound connections to conquest at a time, say like max 10 connections and remaining queued up. so that will be processed later without any issues?


    Is there a mechanism that allows us to control how many inbound and outbound connections you can do threads or total images whatever works.


    whats is the conquest behavior when too many incoming requests come in.?


    Thanks

    akhsuser

Participate now!

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