Condividi tramite

Operations Manager 2007 Health Service Terminated [error 2147500037 (0x80004005)]

  • Articolo

System logs under event viewer would show the below event

Log Name:      System
Source:        Service Control Manager
Date:          8/26/2008 9:06:36 PM
Event ID:      7024
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MS-WS2008.VMDOM.local
Description:
The OpsMgr Health Service service terminated with service-specific error 2147500037 (0x80004005).
Event Xml:
<Event xmlns="https://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7024</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2008-08-26T15:36:36.000Z" />
    <EventRecordID>19674</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>MS-WS2008.VMDOM.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">OpsMgr Health Service</Data>
    <Data Name="param2">2147500037 (0x80004005)</Data>
  </EventData>
</Event>

Solution

  • Enable ETL Verbose Logging from the \Program Files\System Center Operations Manager\Tools Directory by running StartTracing.cmd VER (it is case sensitive)
  • Start the OpsMgr Health Service. It'll fail.
  • Turn off ETL Verbose Logging from the \Program Files\System Center Operations Manager\Tools Directory by running StopTracing.cmd
  • Evaluate the ETL Logs for Health Service

In my case this key was missing:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\State Directory.

It should point to the location in which the agent is installed and the Health Service State subdirectory (\Program Files\System Center Operations Manager\Health Service State). If it is not modify the key. If the key is not present, add the key.

Also check for the following registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\Management Group\<Management Group Name Here>\Windows AccountLockDownSD.

If the WindowsAccoundLockDownSD is not present, export is from a running machine and import is to the bad machine. You could also import it from the operations manager server (this is what I tried).

  • Start the OpsMgr Health Service, it should start at point.

Comments

  • Anonymous
    February 14, 2009
    Thanks fro the solution , I have exported the WindowsAccoundLockDownSD value from win 2003 managment server and the service started ok

  • Anonymous
    June 17, 2009
    Thanks... solved my problem .. for some reason I lost the WindowsAccountLockDownSD binary value ..

  • Anonymous
    December 09, 2009
    THANK YOU!  This solved the problem of the Health Service not starting on one of my DCs.

  • Anonymous
    January 29, 2010
    This is a great article. I never ran in any issues so far, but when a server crashed and I tried to repair it, I started facing this issue. The WindowsAccountLockDownSD key copying from the mgmt server did the trick. Thanks a lot for this. Is there any article on how to read the ETL logs? Thanks Sameer