OpsMgr Health Service fails to start on your Management or Root Management Server

While installing System Center Operations Manager 2007 on a new Server 2008 box with all the patches my health service was failing.  After researching I noticed that that problem was because the OpsMgr Health Service and the OpsMgr SDK Service was trying to start before the Netlogon service was running.  This is due to spanning tree running my network switches.  Here were the errors I was getting.


Event ID:  20056
Description: Failed to initialize the IPC channels for other processes to communicate. The HealthService might fail to start.


Event ID:  2000

Description: The Management Group MYGROUP failed to start.  The error message is Unspecified error
(0x80004005).  A previous message with more detail may have been logged.
Event ID:  2001

Description: No Management Group could be started.  See previous errors for more specific details.  If no errors are present, verify the machine has sufficient memory and has at least one Management Group configured.  Because Active Directory Integration is disabled, the Health Service will not remain running.

To quickly fix the problem in Server 2008 I set my services to delayed start.  (The Service Control Manager starts services that are configured for delayed automatic start after all of the automatic-start threads have finished starting.)  http://blogs.technet.com/askperf/archive/2008/02/02/ws2008-startup-processes-and-delayed-automatic-start.aspx



To fix the problem in Server 2003 set the OpsMgr Health Service and the OpsMgr SDK Service to be dependent on the Netlogon Service. Here are in instructions http://support.microsoft.com/kb/193888

No comments yet.

Leave a Reply