less than 1 minute read

I had the following issue on one of my servers

“The System Center Management service terminated with service-specific error %%-2147467259” when I wanted to start my Healthservice.



When searching the internet I found the following blogpost http://blogs.technet.com/b/smsandmom/archive/2008/04/30/opsmgr-2007-healthservice-service-fails-to-start-with-25362-warning.aspx  . The blogposts says that the State directory registry key can be corrupt but that was fine in my case.

But at the end of the blogpost I found my solution:

This error can be caused by the WindowsAccountLockDownSD Key in at HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesHealthServiceParametersManagement Group being invalid or non-present.  And indeed, that was my issue: the WindowsAccountLockDownSD Key was missing on my server.



The easiest way to resolve the issue with the Windows AccountLockDownSD key is to export the registry key from a similar, working system and then import it in to the registry of the server experiencing the problem.  Once this is complete the HealthService should start successfully.




Alexandre Verkinderen

Leave a comment