Failures when running as service

  • Hello All,


    I have had repeated, unexpected failures with a server running 1.4.14 as a Windows service. The log files reveal no info, but the service unexpected stops. The Windows event viewer only showed one entry that dgate had failed, though this had happened more than once. The dicomserver log file shows no information related to the failure. The strange thing is, I have multiple servers running Conquest as a service but occasionally I have a machine where it doesn't run reliably as a service.


    Are there any known issues with installing => uninstalling => reinstalling Conquest as a Windows Service or is there something else I need to look at.


    The server is running Windows 2003 Server R2 Standard.


    Thanks very much. This is a great meeting place.

  • Hello Marcel,


    Thanks very much for your reply.


    Here is the info from the Event Viewer:


    Faulting application dgate.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x0004afb2.


    From bottom section:


    In bytes:
    0000: 41 70 70 6c 69 63 61 74 Applicat
    0008: 69 6f 6e 20 46 61 69 6c ion Fail
    0010: 75 72 65 20 20 64 67 61 ure dga
    0018: 74 65 2e 65 78 65 20 30 te.exe 0
    0020: 2e 30 2e 30 2e 30 20 69 .0.0.0 i
    0028: 6e 20 6e 74 64 6c 6c 2e n ntdll.
    0030: 64 6c 6c 20 35 2e 32 2e dll 5.2.
    0038: 33 37 39 30 2e 33 39 35 3790.395
    0040: 39 20 61 74 20 6f 66 66 9 at off
    0048: 73 65 74 20 30 30 30 34 set 0004
    0050: 61 66 62 32 afb2


    In words:
    0000: 6c707041 74616369 206e6f69 6c696146
    0010: 20657275 61676420 652e6574 30206578
    0020: 302e302e 6920302e 746e206e 2e6c6c64
    0030: 206c6c64 2e322e35 30393733 3539332e
    0040: 74612039 66666f20 20746573 34303030
    0050: 32626661

  • Hi,


    this does not help much, because the crash is not in the server but in a windows DLL. It could be related to your database configuration. MyODBC is known to cause trouble.... What do you use?


    Marcel

  • Hi,


    hmmm. So the database is not the culprit. This will be hard to debug. Is there any possibility to get a more elaborate crash log. A stack trace would be great. If uou have visual studio (the free express edition is fine), you can attach it to the dgate process and get a more complete debug log when it crashes.


    Marcel

  • Marcel,


    Let me see about doing that. Yeah, this is a strange issue. I could have two identical servers running Conquest as a service. One will have no problems at all, the other would chronically crash.


    I'll check into getting more details on the crashing to you.


    Thanks very much...

  • There seems to be a couple of versions of Visual Studio Express. Which one should I use? I haven't worked with Visual Studio before.


    Until then, here are Event Viewer entries from different server that crashed when running as a service. This one is using 1.4.12c, Windows Server 2003. It's been very reliable and this is the first failure in about 8 months.


    Event Viewer:
    Faulting application dgate.exe, version 0.0.0.0, faulting module dgate.exe, version 0.0.0.0, fault address 0x00050fcc


    Dr. Watson:
    The application, C:\dicomserver\dgate.exe, generated an application error The error occurred on 10/16/2008 @ 17:19:55.906 The exception generated was c0000005 at address 00450FCC (dgate)

  • I have had similar issues with this. One machine running multiple instances kept giving frequent crashes, and on other machines Conquest would run fine.


    My issue came out to be hardware related with the disk, and nothing to do with the Conquest software. After changing the disk and re-installing everything all instances on that machine is running smoothly as a service.


    So perhaps your issue is not Conquest related but something else :D


    Louis

Participate now!

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