locked
OpsMgr Health Service behaviour? RRS feed

  • Question

  • Dear specialists,

     

    I'm facing a problem concerning the OpsMgr Health Service, the following trace is found in the eventlog;

     

    Code Snippet

    Event Type: Information
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7035
    Date:  11/5/2008
    Time:  4:24:31 PM
    Description: The OpsMgr Health Service service was successfully sent a start control.


    Event Type: Information
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7036
    Date:  11/5/2008
    Time:  4:24:36 PM
    Description: The OpsMgr Health Service service entered the running state.


    Event Type: Information
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7035
    Date:  11/5/2008
    Time:  4:32:03 PM
    Description: The OpsMgr Health Service service was successfully sent a stop control.

     

     

    It repeats this cycle infinitely. Question 1: Is this normal?

     

    The service is set to 'restart the service' when failed. This can only be done 3 times by Windows automatically (using services.msc).

     

    After failing it occasionally throws this error:

    Code Snippet
    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7031
    Date:  11/5/2008
    Time:  4:32:18 PM
    Description: The OpsMgr Health Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.

     

     

    Or:

    Code Snippet


    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7034
    Date:  11/5/2008
    Time:  2:29:58 PM
    Description: The OpsMgr Health Service service terminated unexpectedly.  It has done this 9 time(s).

     

     

    Unfortunately, as you can see, it won't restart the service anymore and the servers are unprotected.

    Question 2: Is there a way to force the service to auto-restart or perhaps better: to prevent the service from failing in the first place?

     

    The OPERATIONS MANAGER system log doesn't provide any additional info other than system services failing and throwing errors at SC, but this shouldn't cause OpsMgr agents to fail should it??

     

    Thanks in advance!

    Regards,

    Jeroen

    Wednesday, November 5, 2008 4:05 PM

Answers

  • Hi Jeroen,


    It is not normal if the OpsMgr service always terminated unexpectedly. Please post the below information for further research.


    1. What is the software? SCE or SCOM? With or without SP1 installed?

    2. Did this issue happen on a server or an agent?

    3. What is the OS on the problematic machine?


    For general OpsMgr Health Service startup problem of SCE 2007, please try the below steps one by one to try to fix this issue.

     

     

    #1. Please delete the files under folder “\..\System Center Essentials 2007\Health Service State\Health Service Store” and then try to start the health service.

            Note: Please make a backup before deleting these files.

     

    #2. Try to uninstall the application LogMeIn and restart the server, and then observe the Health Service again.

     

    #3. Let's perform a Clean Boot. A Clean Boot will allow us to isolate any device drivers or programs that are loading at startup that may be causing a conflict with other device drivers or programs that are installed in your computer.

     

    1) Run MSCONFIG.EXE. (MSCONFIG is a built-in tool for Windows XP\2003 systems.)

     

    2) In the Services tab, click "Hide All Microsoft Services" and click "Disable All".

     

    3) In the Startup tab, click "Disable All". Click OK. (This will temporarily prevent third-party programs from running automatically during start-up.)

     

    4) Restart the computer.

     

    If the problem does not occur, it indicates that the problem is related to one application or service we have disabled. You can use the MSCONFIG tool again to re-enable the disabled item one by one to find out the culprit.

     

    #4. To check whether SQL Server Broker Service  has started. The SQL Server Broker Service can be checked with the following query.

    1. Open SQL Management Studio

    2. select New Query
    3. Type: SELECT is_broker_enabled FROM sys.databases WHERE name = 'OperationsManager'
    4. Execute the query.

    If the results return a 0 then the Broker Service is disabled.


    To enable the service execute the following:


    1. Stop all of the Ops Manager services on the RMS and other management servers.
    Note: if you don't stop the services before you run the query it executes forever (hangs).

    2. Open a new query in SQL management studio and type the following:


    ALTER DATABASE OperationsManager SET ENABLE_BROKER

    3. Restart the Ops Manager services.

    Now run the original query again and you should see a 1 telling you the service is
    enabled.


     

    Also please check the RAM for the SCE server. We recommend to install SCE on computers with 2G RAM.


    Thanks,

    Friday, November 7, 2008 8:29 AM