This should allow the service to recover gracefully after it has crashed and should prevent the machine from hanging. Set first failure to restart the service Set the restart time to 15 minutes This work around should stop the server from hanging up: Without this information we cannot determine why the service crashed or how to fix the issue. In order to get to the bottom of this issue we will require a crash dump be collected for the agent service terminating. I'm sorry for the issue were you machine became unresponsive after the VIRPE agent service crashed. "Your case was escalated to me for handling. VIPRE sent me a workaround and wants me to capture the application crash for them to look at. After reviewing the logs this morning each had the following log entry around the time the systems locked up:įaulting application SBAMSvc.exe, version. I had two workstations lock up on me yesterday, requiring a hard boot to get the employees working again. Report Id: 941efd9e-5040-11e3-a15c-005056a100d5ĭistributedCOM Event 10010 - The server did not register with DCOM within the required timeout. 0, time stamp: 0x51a7ce15įaulting application start time: 0x01cee371d7c4fd8eįaulting application path: D:\Program Files (x86)\GFI Software\GFIAgent\SBAMSvc.exeįaulting module path: D:\Program Files (x86)\GFI Software\GFIAgent\SBAMSvc.exe 0, time stamp: 0x51a7ce15įaulting module name: SBAMSvc.exe, version. hr = 0x80070539, The security ID structure is invalid.įaulting application name: SBAMSvc.exe, version. Prior to having to power cycle the following errors are in the event log. I have very little experience with VMware and how to patch it. I'm not sure if VMware is completely patched, my guess would be no. The OS on the terminal servers is Server 2008 R2 64bit.
0 kommentar(er)
