The Health service does not start after you install the RemotelyAnywhere program on the Root Management Server in System Center Operations Manager 2007

Article translations Article translations
Article ID: 942168 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

After you install the RemotelyAnywhere third-party program for remote server management on the Root Management Server, the Health service does not start in Microsoft System Center Operations Manager 2007.

Additionally, the following events may be logged in the System Center Operations Manager 2007 event log:
Event 103: HealthService (5080) Health Service Store: The database engine stopped the instance (0).
Event 101: HealthService (5080) The database engine stopped.

CAUSE

This issue occurs because installing RemotelyAnywhere on Root Management Server corrupts the error code state. Therefore, the Health service cannot run.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, the hotfix installation process restarts the OpsMgr Health service.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Hotfix installation instructions

This hotfix must be installed on each computer that meets any of the following criteria:
  • The computer is a System Center Operations Manager agent.
  • The computer is a System Center Management Server.
  • The computer is a System Center Root Management Server.
  • The computer is a System Center gateway server.
To do this, copy the SystemCenterOperationsManager2007-RTM-KB942168-X86-x64-ENU.msi file from the hotfix package to a local folder or to a shared folder. Then, run this file.

Note You can run this file in Windows Explorer or at a command prompt. The hotfix installation process restarts the OpsMgr Health service.

The agent computers are updated automatically. However, you must approve the update in the "Pending Management" folder. To do this, follow these steps:
  1. On the computer that is running the Management Server role, click Start, point to All Programs, point to System Center Operations Manager 2007, and then click Operations Console.
  2. Select the Administration view, expand Administration, expand Device Management, and then click Pending Management.
  3. In the "Pending Management" folder, review and approve the agent computers on which you want to apply this hotfix.
Note If you install the Operations Manager 2007 agent on a computer after you apply this hotfix, make sure that you approve the installation in the "Pending Management" folder.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
System Center Operations Manager 2007, x86-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Healthservice.dll6.0.5000.381,262,64812-Oct-200718:52
System Center Operations Manager 2007, x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Healthservice.dll6.0.5000.382,555,44812-Oct-200718:53
Microsoft.enterprisemanagement.operationsmanager.dll6.0.5000.312,166,78412-Oct-200718:52
Microsoft.enterprisemanagement.operationsmanager.sdkbin.dll6.0.5000.312,166,78412-Oct-200718:52
Momperfsnapshothelper.exe6.0.5000.047,10412-Oct-200718:53
Momperfsnapshothelperproxy.dll6.0.5000.011,77612-Oct-200718:53

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Properties

Article ID: 942168 - Last Review: February 22, 2008 - Revision: 1.1
APPLIES TO
  • Microsoft System Center Operations Manager 2007
Keywords: 
kbautohotfix kb3rdparty kbhotfixserver kbqfe kbfix kbbug kbprb KB942168

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com