![]() 0 which has given me engine version 1.0 and that has so far not died with definition version 1.171.1.0. Not be started because no user is logged on.Ĭheck the documentation index for 'Just-in-time debugging, errors' for moreĪ possible temporary workaround seems to be to uninstall SCEP and revert to the older Forefront Client Security. Just-In-Timeĭebugging this exception failed with the following error: Debugger could on some servers with SQL Server 2005 management tools installed I’m seeing: Event Type: ErrorĪn unhandled win32 exception occurred in MsMpEng.exe. ![]() There is nothing posted to the Application event log unless you have some kind of debugger installed, e.g. The Microsoft Antimalware Service service terminated unexpectedly. The following event is posted into the System event log: Event Type: Error ![]() It seems as though it is the definition change which is causing the problems. The virus and spyware definitions were updated from version 1.169.2706.0 to 1.171.1.0 overnight. The version of SCEP I have running is 4.5.216.0, although I tried uninstalling and reinstalling, which reverted it back to 4.3.220.0 and that has the same problem. So far all the servers are running Windows Server 2003 32-bit. The service control manager restarts it but it dies again fairly quickly. Have had various servers this morning with the Microsoft System Center Endpoint Protection Client service msmpsvc.exe terminating frequently.
0 Comments
Leave a Reply. |