Microsoft Monitoring Agent Service freezes during the startup process

ينطبق على: System Center 2012 R2 Operations ManagerMicrosoft System Center 2012 Operations Manager Service Pack 1


In System Center 2012 R2 Operations Manager (OpsMgr 2012 R2), the Microsoft Monitoring Agent service, also known as HealthService.exe, gets stuck in the Starting state in Service Control Manager. In this situation, you can't stop the service through Service Control Manager or by using a command prompt. If you manually end the Healthservice.exe process in Task Manager and then try to restart the service, the problem recurs.


During startup, the Microsoft Monitoring agent tries to write to the Operations Manager log. If the Windows Event Viewer Log service is not running or cannot start because of event log corruption, the Microsoft Monitoring Agent gets stuck in the Starting state.


To resolve this issue, follow these steps:
  1. Make sure that the Operations Manager Services accounts have the appropriate permissions on the server. For more information about this, see SCOM 2012 SP1 security accounts matrix.
  2. Locate the Windows Event Log folder on your Windows server (for example, %SystemRoot%\System32\winevt\Logs), and then back up the existing event logs in another location.
  3. Delete the existing Event Log files, then restart the Event Viewer Log service and the Microsoft Monitoring Agent service, in that order.

More Information

The Microsoft Monitoring Agent service was known as System Center Management in versions before OpsMgr 2012 R2. 

This article applies to System Center Operations Manager 2012 R2.