Microsoft KB Archive/901049

= Event ID: 22061 errors appear repeatedly in the Application log on a Microsoft Operations Manager Management Server =

Article ID: 901049

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Operations Manager (MOM) 2005

-





INTRODUCTION
''This article describes an issue where Event ID: 22061 appears repeatedly in the Application log on a Microsoft Operations Manager (MOM) Management Server. Additionally, this article describes how to perform the following tasks:''


 * How to troubleshoot Event ID: 22061 errors that may appear in the Application log on a Microsoft Operations Manager (MOM) 2005 Management Server.
 * How to turn on data logging on the MOM Management Server.
 * How to use the GUID information that is contained in the Dbconnector.xml log file to locate the corresponding MOM Rule.



SYMPTOMS
If you install Microsoft Operations Manager (MOM) 2005, the following event may appear repeatedly in the Application log on the MOM Management Server:

Event ID: 22061 The Server outgoing data processing has been blocked. This indicates problems with communication or database processing.

This symptom occurs when a MOM service discovery script runs and collects lots of data from one or more servers.



CAUSE
This issue occurs because the MOM Management Server may block data processing of other data during the insertion of the service discovery data. For example, this problem can occur when the MOM DNS Service Discovery script runs. The MOM DNS Service Discovery script collects DNS zone information. When the MOM DNS Service Discovery script runs, the MOM DNS Service Discovery script receives lots of DNS zone data from many DNS servers. This issue may also occur if the MOM Active Directory Topology Discovery script runs and receives lots of data.

In these cases, the MOM Management Server is busy inserting lots of service discovery data. The data insertion task can take several minutes or longer. The time that the data insertion task takes depends on how much data is collected. During the insertion of the service discovery data, the MOM Management Server may block data processing of other data. The MOM Management Server blocks data processing of other data until it processes the service discovery data.



RESOLUTION
To resolve this issue, determine whether lots of service discovery information was inserted into the MOM Database. To do this, follow these steps.

Turn on data logging
Note After you turn on data logging, you may notice decreased performance on the MOM Management Server. Additionally, after you turn on data logging, the Dbconnector.xml log file may become very large. Therefore, we recommend that you disable data logging after this issue is resolved.  Log on to the MOM Management Server by using an account that has administrative permissions. Click Start, click Run, type regedit in the Open box, and then click OK. Locate and then right-click the following subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint\Configurations\ \Operations\Consolidator\Database Insertion

 Click New, click DWORD Value, type DataLogging, and then press ENTER. Double-click DataLogging. In the Value Data box, type 2, click to select Decimal under Base, and then click OK.</li> Restart the MOM Management Server.</li></ol>

By default, after you turn on data logging, the Dbconnector.xml log file is located in the \Temp\Microsoft Operations Manager folder on the MOM Management Server.

How to use the Dbconnector.xml log file to locate the MOM rule script
You can use the Dbconnector.xml log file to help locate the MOM rule script that is causing the time-out. To do this, follow these steps: <ol> Log on to the MOM Management Server by using an account that has administrative permissions.</li> Open the \Temp\Microsoft Operations Manager folder on the MOM Management Server.</li> Double-click the DbconnectorLog.xml log file.</li>  Examine the log file and look for a DataItem keyword with an unusually large value for the time= value, where the RuleID value contains the GUID. For example: '

</li> Click Execute Query to run the query.</li> In this example, SQL Query Analyzer should return the following data that is based on the GUID value: DNS Service Discovery </li></ol>

Modifying the MOM event rule
In this example, we have determined that the DNS Service Discovery event rule is experiencing a longer than ordinary time= value.

By default, the DNS Service Discovery event rule runs every 30 minutes. In an environment where the DNS Service Discovery script collects lots of information, the MOM Management Server may experience communication problems when the DNS zone information is processed.

To resolve this problem, either disable the event or modify the event rule to run less frequently. To do this, follow these steps:
 * 1) Log on to the MOM Management Server by using an account that has administrative permissions.
 * 2) Click Start, point to Programs, point to Microsoft Operations Manager 2005, and then click Administrator Console.
 * 3) In the MOM Administrator Console, expand Microsoft Operations Manager , expand Management Packs, right-click Rule Groups, and then click Find Rules.
 * 4) In the Rule Search dialog box, click to selectAll Rule Groups, and then click Next.
 * 5) On the Specify the search criteria page, click Rule name, click matches wild card, and then type DNS Service Discovery in the box next to matches wild card.
 * 6) Click All rule types under Rule type, click Next, two times, and then click Finish.
 * 7) Double-click the DNS Service Discovery event rule.

Note You find two DNS Service Discovery event rules. One is for Windows 2000-based DNS Server. The other is for Windows 2003-based DNS Server.
 * 1) In the Event Rule Properties  - DNS Service Discovery dialog box, click the Data Provider tab. Under Provider type, click Modify.
 * 2) In the Timed Event Provider Properties dialog box, type 1 in the box next to Generate event every.
 * 3) Click days, and then click OK two times.

In this example, the DNS Service Discovery event rule runs one time per day instead of every 30 minutes.

Note Even after changing the event rule frequency to one time a day you might still see event 22061 in the error logs. This may occur one time each day when this rule runs depending on the load at that time.

Keywords: kbtshoot kbprb KB901049

-

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

© Microsoft Corporation. All rights reserved.