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

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.

1. Log on to the MOM Management Server by using an account that has administrative permissions.
2. Click Start, click Run, type regedit in the Open box, and then click OK.
3. Locate and then right-click the following subkey:

   HKEY_LOCAL_MACHINE\SOFTWARE\Mission Critical Software\OnePoint\Configurations\name of the MOM management group\Operations\Consolidator\Database Insertion

4. Click New, click DWORD Value, type DataLogging, and then press ENTER.
5. Double-click DataLogging.
6. In the Value Data box, type 2, click to select Decimal under Base, and then click OK.
7. Restart the MOM Management Server.

By default, after you turn on data logging, the Dbconnector.xml log file is located in the %windir%\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:

1. Log on to the MOM Management Server by using an account that has administrative permissions.
2. Open the %windir%\Temp\Microsoft Operations Manager folder on the MOM Management Server.
3. Double-click the DbconnectorLog.xml log file.
4. 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:

   <DataItem TYPEID="{79CBB19C-A897-440F-8E99-28C2649745AC}" now="6/16/2005 11:10:01" time="1630.541">
   
           <Discovery>
   
               <InstanceID>{25CAB4BC-6932-4C0D-8B93-113ED8CE427E}</InstanceID>
   
               <ProviderID>{F320DA51-13BF-11D3-B2CD-00A0C92A28B4}</ProviderID>
   
               <ProviderName>Script Provider</ProviderName>
   
               <Time TimeString="6/16/2005 11:10:01">38519.7569573895</Time>
   
               <Computer>ComputerName</Computer>
   
               <RuleID>{6081A66F-6B48-417B-B237-6FB26E75732E}</RuleID>
   
   

   In this example, the RuleID value is {6081A66F-6B48-417B-B237-6FB26E75732E}. This value is the GUID that identifies the MOM Rule. Also in this example, the DataItem has a very high time value of 1630.541.

How to use the GUID to identify the MOM rule script

You can use the GUID that is referenced in the DbconnectorLog.xml file to determine the MOM rule that has the high time= value. To do this, follow these steps:

1. Log on to the computer that is hosting the MOM OnePoint database by using an account that has administrative permissions.
2. Click Start, point to Programs, point to Microsoft SQL Server, and then click Query Analyzer.
3. In SQL Query Analyzer, click the OnePoint database in the database list, and then copy the following SQL statement to the Query window:

   select name Rule_Name, idprocessrule ruleid
   from processrule
   Where idprocessrule = 'the GUID that you determined from the DBConnectorLog.xml file'

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

   Rule_Name	ruleid
   DNS Service Discovery	6081A66F-6B48-417B-B237-6FB26E75732E

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 (ServerName), 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.
8. In the Event Rule Properties (ServerName) - DNS Service Discovery dialog box, click the Data Provider tab. Under Provider type, click Modify.
9. In the Timed Event Provider Properties dialog box, type 1 in the box next to Generate event every.
10. 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.