what is the reason behind window service stopped ,whether its due to LAN problems or any other issues

Posted by Steve on Super User See other posts from Super User or by Steve
Published on 2011-11-28T07:49:21Z Indexed on 2011/11/28 10:04 UTC
Read the original article Hit count: 255

I have a windowservice which named Trunk which stopped one day i just want to know the reason behind it? this is an entry in the logs,

Nov 15 17:54:04.318 :Trunk-1516:Trunk:handle_control_event:Received CTRL_LOGOFF_EVENT,  ignore it

Nov 25 15:54:52.157 :Trunk-1516:Trunk:ERROR - Process Restart Count (5) Exceeded for:C:\Program Files\secon\11.1.4\bin\vmd

Nov 25 15:54:52.157 :Trunk-1516:Trunk:Stopping Trunk  ...
Nov 25 15:54:52.314 :Trunk-1516:Trunk:Shutting down, signaled C:\Program F
Nov 20 15:54:20.345 :SCBridge.RegisterBridge:Exception in method:
ScUtility.ScCommandException (0xa08990002): Exception from HRESULT:
0xa08990002
Supplemental Information:
None available.
   at ScServer.ScServiceProcessorRegistryManager.Attach(String
serviceProcessor, ScClientInformation clientInfo, FORCE_ATTACH_SPEC
forceAttachToMaster)
   at ScServer.ScServiceProcessorRegistry.Attach(String serviceProcessor,
Object clientInfo)
   at ScServer.ScServiceProcessorRegistry.Attach(String serviceProcessor)
   at ServerControlInterface.SCBridge.RegisterBridge(String SPName) for
system APOLLOSP0 attempting to attach and register with the Bridge

i had seen service is registered with specific account, so i thought that user logged off from the machine that may be the reason behind it or any LAN disconnection problem . But Having taken another look at the above entry we seem to have a constant failure being generated in vmd which causes Trunk to detect vmd requires a restart. Most of the time it works OK and the restart count is anything up to 4. In this case the Trunk log confirms that the Restart Count is 5 and so is considered to be exceeded. Presumably, this triggers the termination of the other services and Trunk is actually doing its job.So, coould this just be a timing issue and we need to increase the tolerance level (i.e restart count) or do we need to address the 0xa08990002 error in vmd?

© Super User or respective owner

Related posts about windows-server-2003

Related posts about windows-services