Earlier this week, I was asked to deal with a server where xcomd stopped running.
The server is Windows 2016, xcom version is 11.6.02 (64 bit).
Whenever I started it, it came up for a few seconds, wrote a message to xcom.log, and then went down.
Each time, it wrote a record the the Event Viewer (see below).
Restarts did not help, so I tried to uninstall/install XCOM.
The un-install step failed, it said that xcomd is still in use.
Only when I killed application processes one by one from the Task Manager, I was eventually able to uninstall/install.
Then, xcomd resumed working.
I am not able to reproduce the problem, but I thought you might advise me, what to do next time this happens?
The Event Viewer record was as follows:
Faulting application name: xcomd.exe, version: 0.0.0.0, time stamp: 0x59c23b57
Faulting module name: ntdll.dll, version: 10.0.14393.2969, time stamp: 0x5ccd148a
Exception code: 0xc0000005
Fault offset: 0x000000000002dd60
Faulting process id: 0xb50
Faulting application start time: 0x01d5713ba3e343be
Faulting application path: C:\xcomnt\xcomd.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 708232af-c769-40c3-9290-8c8a21fb3766
Faulting package full name:
Faulting package-relative application ID: