none
The OpsMgr Health Service service terminated with service-specific error 3

    Question

  • Hi SME,

    One of our agents have gone offline due to some unknown reason. When we try restarting the health service we get the below error.

    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7024
    Date:  30/07/2013
    Time:  16:11:59
    User:  N/A
    Computer: Server name
    Description:
    The OpsMgr Health Service service terminated with service-specific error 3.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    I have tried following the below link to resolve the issue.

    http://blogs.technet.com/b/smsandmom/archive/2008/04/30/opsmgr-2007-healthservice-service-fails-to-start-with-25362-warning.aspx

    The ETL Logs return the below error

    0              00000000             [6]0.6560::07/30/2013-13:10:51.526 [HealthServiceExecutive]  Error CHealthServiceExecutive::CheckAndCreateTempDirectory(HealthServiceExecutive_cpp1142)CreateDirectory on path "D:\temp\\Health Service" failed with code 3(ERROR_PATH_NOT_FOUND).

    I do not have D drive on my server. Please advise how do i change the config.

    Jesty


    Jesty


    • Edited by Jesty_s Thursday, August 01, 2013 10:06 AM comfidential
    Tuesday, July 30, 2013 3:44 PM

All replies

  • Hi,

    Firstly, please try to clear the cache of the agent:

    How and When to Clear the Cache

    http://technet.microsoft.com/en-us/library/hh212884.aspx

    If this does not work, please try reinstalling the agent.

    Thanks.


    Nicholas Li
    TechNet Community Support

    Wednesday, July 31, 2013 1:37 PM
  • Hi Nicholas,

    I get the below error.

    Health Service 'Servername' in which the location monitoring object is contained is not available. Make sure that the computer hosting the Health Service is available and verify that the Health Service is running.

    Please assist


    Jesty


    • Edited by Jesty_s Thursday, August 01, 2013 10:06 AM confidential
    Wednesday, July 31, 2013 4:09 PM
  • Yes and i had reinstalled the agent. but that too seems not working.

    Jesty

    Wednesday, July 31, 2013 4:18 PM
  • Hi,

    it looks like the system %TEMP% variable is pointing to the wrong folder. Can you check this?


    http://OpsMgr.ru/

    Wednesday, July 31, 2013 6:02 PM
  • Hi Alexey,

    I have run sysdm.cpl and have checked the System variables. The Tmp and temp was pointing to D and C drive respectively.

    Temp   C:\WINNT\TEMP

    TMP     D:\............ which i dont remember now.

    i have edited this to C:\temp and applied. But still unable to start the OpsMgr health service.

    The server is a 2000 Sp4 server. Please advise.


    Jesty

    Thursday, August 01, 2013 8:21 AM
  • Can you post the full OpsMgr version you are using?

    http://OpsMgr.ru/

    Thursday, August 01, 2013 8:23 AM
  • We are using SCOM 2007 Sp1 Cu1 and the server is in DMZ zone managed by the Gateway server.

    Please let me know if you need more details.


    Jesty

    Thursday, August 01, 2013 8:58 AM
  • Hi Jesty,

    was the server rebooted after the System variables were edited?

    Thursday, August 01, 2013 9:20 AM
  • No it was not. Is it mandatory for the server to be rebooted after the system variables are amended?

    Jesty

    Thursday, August 01, 2013 10:35 AM
  • It has been a problem for me.

    But it is worth a try. After all, nothing fixes a windows machine than a reboot :)

    Thursday, August 01, 2013 10:55 AM
  • Hi Jetsy,

    As you stated at the beginning of this post, that you followed this Technet Blog Article

    http://blogs.technet.com/b/smsandmom/archive/2008/04/30/opsmgr-2007-healthservice-service-fails-to-start-with-25362-warning.aspx

    Did you get a chance to revisit the Registry locations mentioned?

    The above is looking for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\State Directory.

    If you're using SP1 or later then the path it's looking for will be HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\State Directory.

    5. Verify the value that it contains. 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), change the value to correct location if
    incorrect or create a new String Value (Reg_SZ) if missing and set it to the correct path.

    Additional Info:http://blog.scomskills.com/move-the-health-service-state-directory-on-the-rms/

    Hope that helps :)


    Vikky | "If my reply rendered as answer to you question,kindly click on "Mark as Answer"

    Thursday, August 01, 2013 11:16 AM
  • Hi Vikky,

    I have again checked the location now.

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

    This contains the value where the SCOM healthservice agent is located. But the Health service agent seems to be empty might be because i have reinstalled the agent again on the server.


    Jesty

    Thursday, August 01, 2013 1:04 PM
  • Would someone be able to help me?

    Jesty

    Friday, August 02, 2013 8:17 AM
  • Hi SME,

    Any suggestion is much appreciated.


    Jesty

    Monday, August 05, 2013 6:59 AM