Microsoft KB Archive/885719

= The MOM service may not restart when a computer discovery task runs in Microsoft Operations Manager 2005 =

Article ID: 885719

Article Last Modified on 10/25/2006

-

APPLIES TO


 * Microsoft Operations Manager (MOM) 2005

-



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
In Microsoft Operations Manager (MOM) 2005, the MOM service (MOMService.exe) stops and may not restart when a computer discovery task runs. When this problem occurs, the following events are logged in the application log: Source: Microsoft Operations Manager

Type: Information

ID: 21060

Description:

Computer Discovery started in &quot;FullScanMode&quot; on MOM Server &quot; &quot; for Management Group &quot; &quot;

Source: Microsoft Operations Manager

Type: Information

ID: 21241

Description:

The MOM Server detected a change to the rules for one or more computers, and will begin downloading the new rules and configuration settings to the affected computers.

Source: Microsoft Operations Manager

Type: Information

ID: 9010

Description:

The Microsoft Operations Manager service (MOMService.exe) started.

Source: Microsoft Operations Manager

Type: Information

ID: 9013

Description:

The Microsoft Operations Manager service (MOMService.exe) has stopped.

Events 9013 and 9010 may be logged up to four times before the MOM service stops.



CAUSE
This problem may occur if the following conditions are true:
 * You do not use the Active Directory directory service in your network environment.
 * NetBIOS name resolution is slow or does not respond in your network environment.



MORE INFORMATION
As part of the computer discovery process, MOM 2005 performs a configuration update. The configuration update is logged with event ID 21241. As part of the configuration update process, the MOM service stops. However, because a function that the process calls takes a long time to respond, the MOM service does not restart. The MOM service tries to restart five times. If the function still does not respond, the MOM service stops.



RESOLUTION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this problem, create a registry subkey to specify a longer time-out value for the MOM service. To do this, follow these steps:
 * 1) Click Start, click Run, type regedit, and then click OK.
 * 2) Locate the   subkey.
 * 3) Right-click the OnePoint subkey, point to New, and then click DWORD Value.
 * 4) Name the value ServiceControlTimeOut.
 * 5) Double-click ServiceControlTimeOut, type a value that is greater than 360, and then click OK.

This value indicates how many seconds the MOM service waits before reaching the time-out limit.
 * 1) Stop and then restart the MOM service.

Keywords: kbtshoot kbservice kbactivedirectory kbregistry kberrmsg kbeventlog kbevent kbperformance kbdiscovery KB885719

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.