You may find that the SQL Server process (Sqlservr.exe) causes unusually high CPU usage for a long time. This occurs after you install the Microsoft Availability Reporting Management Pack for Microsoft Operations Manager (MOM) 2005. Additionally, this occurs when the ReliabilityAnalysisReporting scheduled task is running.

This problem occurs when the Microsoft Availability Reporting Management Pack has an event collection rule that contains incorrectly-defined criteria. The rule specifies that all System event log events that meet the following criteria must be collected:

• Event Number equals '7036'
• Source Name equals 'Service Control Manager'

The problem occurs as all the 7036 service Start and Stop events that Microsoft Windows Server 2003 generates are collected. In this situation, the application that the Microsoft Reliability Analysis Service (MRASLoader.exe) scheduled task runs cannot process all the events. This problem may occur during the next ReliabilityAnalysisReporting scheduled task run. This run follows the successful run of the SystemCenterDTSPackageTask scheduled task.

The correct event collection rule specifies that all System event log events that meet the following criteria must be collected:

• Event Number equals '7036'
• Source Name equals 'Service Control Manager'
• Description contains substring 'Microsoft Exchange Information Store'

To resolve this problem, you must modify the rule criteria. To do this, follow these steps:

1. Open the MOM 2005 Administrator console.
2. Expand Management Packs, expand Rule Groups, expand Microsoft Availability Reporting Management Pack for Microsoft Operations Manager 2005, expand System Events, expand Service Control Manager, expand 7036 Series, expand 7036 Start, and then click Event Rules.
3. In the details pane, right-click Microsoft Internet Information Services Reliability Model Events Service Control Information Store, and then click Properties.
4. In the Collect Rules Properties dialog box, click the Criteria tab, and then verify that the following matches the Criteria description:
   • Event Number equals '7036'
   • Source Name equals 'Service Control Manager'
5. Click Advanced.
6. In the Advanced Criteria dialog box, select Description from the Field menu.
7. On the Condition menu, select contains substring.
8. In the Value box, type Microsoft Exchange Information Store, click Add to List, and then click Close.
9. In the Collect Rules Properties dialog box, verify that the following criteria are present, and then click Apply:
   • Event Number equals '7036'
   • Source Name equals 'Service Control Manager'
   • Description contains substring 'Microsoft Exchange Information Store'
10. On the General tab, type Microsoft Exchange Reliability Model Events Service Control Information Store in the Rule Name box, and then click OK.
    
    Note Step 10 is not required for the new rule to function correctly. The rule name that we recommend is more accurate for the behavior of the rule.

This problem is resolved in version 05.0.5000.0000 of the Availability Reporting Management Pack. To obtain this version, visit the following Microsoft Web site:

The previous problem occurs when the following conditions are true:

• The SQL Server process exhibits unusually high CPU usage in the Task Manager Processes list.
• The MRASLoader.exe process is also in the Task Manager Processes list.

If you experience the previous symptoms, we suggest that you follow these steps:

1. Modify the event collection rule as the "Resolution" section discusses to prevent future collection of all the 7036 service Start and Stop events.
2. Open Scheduled Tasks, right-click the ReliabilityAnalysisReporting scheduled task, click Properties, and then click to clear the Enabled (scheduled task runs at specified time) check box.
3. Manually run the scheduled task whenever you are able to wait for a long time. To do this, follow these steps:
   1. Open Scheduled Tasks.
   2. Right-click the ReliabilityAnalysisReporting scheduled task, and then click Run.
      
      Note The task status will change to Running.
4. Let the ReliabilityAnalysisReporting task run until the task finishes.
   
   Note After the ReliabilityAnalysisReporting scheduled task finishes, the Status field will be blank and the value in the Last Result column should be "0x0."
5. After the ReliabilityAnalysisReporting scheduled task finishes, open Scheduled Tasks, right-click the ReliabilityAnalysisReporting scheduled task, click Properties, and then click to select the Enabled (scheduled task runs at specified time) check box.

For more information about SystemCenterDTSPackageTask troubleshooting, click the following article number to view the article in the Microsoft Knowledge Base: