Troubleshooting
Applies To: Operations Manager 2007 R2
The following table describes issues that can occur with the Operations Manager Management Pack and presents possible solutions. For more information about resolving a problem with the Operations Manager Management Pack, see the product release notes. You can also search for the term "Operations Manager Management Pack" on Microsoft Help and Support.
Problem | Solution |
---|---|
When you run the Data Volume by Management Pack or Data Volume by Workflow and Instance reports and drill down into any of the values, an error message states “The 'StartDate_BaseType' parameter is missing a value”. |
On the reporting server, install the cumulative update for SQL Server 2008 (https://go.microsoft.com/fwlink/?LinkID=167699). |
An alert is generated indicating that the script “SCOMpercentageCPUTimeCounter.vbs” failed with an error message that states “Invalid class“. Following is an example of the error message that would be shown in the event description: The process started at 8:11:41 PM failed to create System.PropertyBagData. Errors found in output: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\2767\SCOMpercentageCPUTimeCounter.vbs(125, 5) SWbemRefresher: Invalid class One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.HealthService.SCOMpercentageCPUTimeMonitor Cause: One or more of the WMI classes that the script queries is not loaded properly on the system. The script requires that the following WMI classes be available in the root\cimv2 namespace:
|
Use the following steps to determine which class or classes are not present on the system:
If you do not see one of more of the classes in the query result, follow the steps below.
|
In Operations Manager 2007, a large number of computer groups and a high volume of state changes occurring on computer objects can result in one or both of the following conditions:
|
Every time the state changes on one of the top-level monitors for a computer (for example: Availability, Performance, Security, and Configuration), that state change is rolled up to every computer group of which the computer is a member. This can result in a cascading series of state changes and in environments where the volume of state changes are significant and the number of computer groups rolling up the changes are high. For instructions on resolving this issue, see Knowledge Base article 967537 (https://go.microsoft.com/fwlink/?LinkId=146985). |
The Failed Accessing Windows Event Log monitor is in a warning state even though it has access to the event log. This monitor is disabled by default. If you enable the monitor and it does not have access to the event log, it changes to a warning state (yellow). After you fix the issue by giving the monitor access to the event log, the monitor remains in a warning state even though it should change to a healthy state (green). |
None. It is recommended that you do not enable the monitor. If you have enabled it, you can disable it. |
The connected management group is not forwarding alerts and other monitoring data to the local management group. |
Enable the Tiered Management Group Synthetic Transaction monitor for the connected management group. For instructions, see "Configure a Connected Management Group" in Optional Configuration. |
When the Health Service Heartbeat Failure monitor for agents attempts to recover an agent automatically, access is denied. |
Add a Run As account to the Automatic Agent Management Account Run As profile. The Run As account must have administrator access on the target computers. For instructions, see "Enable recovery for the Health Service Heartbeat Failure Monitor" in Getting Started. |
Notification subscriptions are out of scope. |
Add a Run As account to the Validate Alert Subscription Account Run As profile. The Run As profile requires a Run As account that is a member of the Operations Manager Administrators user role and has administrator access to the root management server. For instructions, see "Add a Run As Account to the Run As Profile for the Validate Alert Subscription Account" in Getting Started. |
The configuration service for the Windows service state does not restart automatically. |
To automatically start the configuration service when it stops, you must enable an override. For instructions, see "Set the Configuration Service to Restart Automatically" in Getting Started. |
The availability health of the Operational Database Watchers Group does not roll up to the management group. |
Enable the Operational Database Watchers Group to Management Group Availability Health Rollup. For instructions, see "Enable the Operational Database Watchers Group to Management Group Availability Health Rollup" in Getting Started. |
Computers running Windows Vista or Windows Server 2008 fail to respond to ping. |
The default firewall settings for computers running Windows Vista or Windows Server 2008 prevent the computers from providing a ping response. The Ping task in Operations Manager and any diagnostic or recovery tasks that use ping will fail when run against a computer running Windows Vista or Windows Server 2008 unless the firewall settings on the computer are configured to allow incoming ICMP traffic. The Ping Status monitor and the Heartbeat Failure monitor use ping. You can disable these monitors for computers running Windows Vista or Windows Server 2008, or you can configure the computers to allow incoming ICMP traffic. For instructions on changing the firewall configuration, see Create an Inbound ICMP Rule on Windows Vista or Windows Server 2008 (https://go.microsoft.com/fwlink/?LinkId=161045). |