OEC 9800 memory error

  • Hello Marcel,


    The OEC 9800 runs without any problem on my old server with an older version of Conquest.

    I have a new server with the latest version of Conquest.

    When I try to send an image to Conquest from the OEC 9800, a memory error occurs on the OEC 9800 that I am told is caused by either the OEC 9800 is being scanned for security or Conquest is trying to install something to the OEC 9800. The OEC 9800 has to be restarted.

    Is Conquest trying to install something onto the OEC 9800 that would cause the OEC 9800 to get a memory error?


    Thank You

  • Hi,


    Conquest does not install anything. Can you try to temporarily disable JPEG support on the new server (that was off by default on older servers). This option allows the OEC 9800 machine to send compressed data if it wants, and maybe it crashes on that.


    Marcel

  • Hi Marcel,


    Yes, it crashes when performing a Verify from the OEC to Conquest.


    Version 1.4.16 works on the SBS-2011 server and fails on the new SBS-2019 server.

    Version 1.5.0 fails on the new SBS-2019 server.


    Here is some Debug information:

    I am hoping this debug information will provide you with some insight into what's going on.


    Debug after issuing an OEC Verify to CONQUEST 1.4.16 on old SBS-2011 server, this works well!


    [CONQUESTSRV1] UPACS THREAD 8: STARTED AT: Wed Sep 29 11:28:45 2021

    [CONQUESTSRV1] Calling Application Title : "OEC_9800A "

    [CONQUESTSRV1] Called Application Title : "CONQUESTSRV1 "

    [CONQUESTSRV1] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 32000

    [CONQUESTSRV1] Presentation Context 0 "1.2.840.10008.1.1" 1

    [CONQUESTSRV1] C-Echo

    [CONQUESTSRV1] UPACS THREAD 8: ENDED AT: Wed Sep 29 11:28:46 2021

    [CONQUESTSRV1] UPACS THREAD 8: TOTAL RUNNING TIME: 1 SECONDS



    Debug after issuing an OEC Verify to CONQUEST 1.4.16 on new SBS-2019 server, this causes an OEC-9800 error!


    [CONQUESTSRV1] Connected by address: de00a8c0

    [CONQUESTSRV1] Testing transfer: '1.2.840.10008.1.2' against list #0 = '1.2.840.10008.1.2'


    I have attached PacsTrouble and serverstatus logs renamed to txt files.


    Any insight is much appreciated.


    Thank You

  • Can you post your dgatesop.lst file?


    "Debug after issuing an OEC Verify to CONQUEST 1.4.16 on new SBS-2019 server" Is that correct? It says 1.4.16.


    The difference is that the 2nd one is bigendian, that may be broken on 1.4.16. Edit: large changes in bigendian code between 1.4.16 and 1.5.0.


    Marcel

Participate now!

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