Export (0) Print
Expand All

Troubleshooting

Updated: August 2, 2010

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 (http://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:

  • Win32_Processor

  • Win32_Process

  • Win32_PerfFormattedData_PerfProc_Process

Use the following steps to determine which class or classes are not present on the system:

  1. Log on to the server via terminal services.

  2. Run the program WBEMTEST.exe.

  3. Click Connect and connect to the root\cimv2 namespace.

  4. Under IwbemServices, click Enum Classes.

  5. In the Superclass Info dialog box, leave the superclass name empty, select Recursive, and click OK.

  6. When Query Results displays the results, scroll through the list and ensure that the three WMI classes are available.

If you do not see one of more of the classes in the query result, follow the steps below.

  1. Run the following command from a command prompt with administrator level permissions:

    WMIADAP /F

  2. Re-check to see if the class or classes are still missing. If they are still missing, run the following commands from a command prompt with administrator level permissions

    cd %windir%\system32

    lodctr /R

  3. Re-check to see if the class or classes are still missing. If one or more are still missing, use the Extensible Counter List Tool (Exctrlst.exe) and check if the PerfProc or PerfOS are disabled, and enable them if they are. You can download the Extensible Counter List Tool from Windows 2000 Resource Kit Tool : Extensible Performance Counter List (http://go.microsoft.com/fwlink/?LinkId=183182).

  4. Re-check to see if the class or classes are still missing. If one or more are still missing, run the following as a batch file.  This will re-register all WMI Modules:

    @echo off
    sc config winmgmt start= disabled
    net stop winmgmt /y
    %systemdrive%
    cd %windir%\system32\wbem
    for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
    regsvr32 %windir%\system32\tscfgwmi.dll
    wmiprvse /regserver 
    winmgmt /regserver 
    net start winmgmt
    
  5. Re-check to see if the class or classes are still missing. If one or more are still missing, contact Microsoft Customer Service and Support.

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:

  • High CPU and disk utilization on the root management server coming from the <<ProcessName(s)>> process.

    This is the Health Service process.

  • Queues back up (<<Provide counter name>>) on the gateway, management server, and root management server system(s).    

    This is the counter \Health Service Management Groups(Management Group Name)\Send Queue % Used.

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 (http://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 (http://go.microsoft.com/fwlink/?LinkId=161045).

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft