Microsoft KB Archive/885735

= The MOM service on MOM 2005 Management Server computers cannot start when you try to monitor agentless managed computers =

Article ID: 885735

Article Last Modified on 10/25/2006

-

APPLIES TO


 * Microsoft Operations Manager (MOM) 2005

-





SYMPTOMS
When you use Microsoft Operations Manager (MOM) 2005 to manage computers that do not have the MOM 2005 agent installed, the MOM service on a MOM 2005 Management Server computer may not start successfully. Computers that do not have the MOM 2005 agent installed are known as agentless managed computers.



CAUSE
This issue occurs when you monitor a computer by using MOM agentless monitoring. By default, when a Management Server computer tries to monitor a Microsoft Windows Server 2003-based computer by using agentless monitoring, the connection time-out value is 120 seconds. For computers that are running Microsoft Windows NT 4.0 or Microsoft Windows 2000, the connection time-out value is 60 seconds. The 60-second and 120-second time-out values are based on the default time-out values of the Windows Management Instrumentation (WMI) provider. By default, the MOM service has a time-out value of 60 seconds, and in this case, the MOM service on the Management Server computer may time out before the connection to the agentless managed computer has timed out.

This issue typically occurs when one of the following conditions is true:
 * The Management Server computer does not have the correct credentials to contact the MOM agentless managed computer.
 * The agentless managed computer is not online or other problems exist with remote connectivity between the Management Server computer and the agentless managed computer.

When the MOM service on the Management Server computer stops, you must manually restart the service. If there are no other Management Server computers available in the Management group, computers that are running the MOM agent cannot send data to the MOM database. To manually restart the MOM service, follow these steps:
 * 1) Click Start, point to Programs, point to Administrative Tools, and then click Services.
 * 2) In the Services snap-in, right-click MOM, and then click Start.
 * 3) Close the Services snap-in.

Note MOM agent computers use a local cache to store the data that the computers cannot send until they contact the Management Server computer. The amount of data that an agent computer can cache after it can no longer contact the Management Server computer depends on various factors. These factors include the size of the computer cache and the number of event and alert rule matches that are stored in the cache over time.



WORKAROUND
To work around this issue, increase the service control time-out for the MOM service on the Management Server computer. To do this, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate and then right-click the following registry sub key:

\HKEY_LOCAL_MACHINE\Software\Mission Critical Software\Onepoint

 Click New, and then click DWORD Value. Type ServiceControlTimeOut for the DWORD value name. Double-click the ServiceControlTimeOut DWORD value. In the Edit DWORD Value dialog box, click to enable Decimal, and then enter a value that is high enough to enable the MOM service to successfully start. For example, if you are monitoring a Windows Server 2003-based computer that is using agentless monitoring, enter a value that is more than 120 seconds, such as 200 or 240 .</li></ol>

Additional query words: MOM 2005, MOM Service

Keywords: kbprb kbtshoot KB885735

-

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

© Microsoft Corporation. All rights reserved.