Operations Manager agents with teamed network adapters fail to be discovered and monitored

Article ID: 2847767 - View products that this article applies to.
Expand all | Collapse all

Symptoms

System Center Operations Manager 2007 R2 agent computers that utilize NIC teaming are not discovered or monitored and you see the following errors:

Log Name:       Operations Manager
Source:            Health Service Script
Date:               <date>
Event ID:          4001
Task Category: None
Level:              Error
Keywords:       Classic
User:              N/A
Computer:      <computerName>
Description: Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs : The class name 'Win32_PerfFormattedData_Tcpip_NetworkInterface Where Name ='VLAN100:HP Network Team _1'' did not return any valid instances.  Please check to see if this is a valid WMI class name.. Invalid class

You may also see the following alert:

The process started at 09:44:43 failed to create System.PropertyBagData, no errors detected in the output. The process exited with 0
Command executed: "C:\Windows\system32\cscript.exe" /nologo "Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs"
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 23\\
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.Server.2008.NetworkAdapter.PercentBandwidthUsedTotal.Collection
Instance name: Local Area Connection
Instance ID: {}

Cause

This can occur if the drivers being used for NIC teaming on the agent do not properly register in WMI.

The Base OS Management Pack (version 6.0.6958.0) contains a script that is responsible for discovering teamed adapters named Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs. If the NIC teaming driver being used fails to properly register in WMI, when the script runs and fails to find the registered classes the script will fail and log the errors above. 

Many teaming NIC drivers also fail to register performance counters which can also be a reason why the required WMI registration is not created.

Resolution

If you experience script failures such as these, disabling NIC teaming on the agent computer will resolve the issue. The problem with the NIC registration in WMI needs to be addressed by the NIC manufacturer so that the driver correctly register itself in WMI when installed. Please contact the adapter manufacturer for more information.

More Information

There is more information on this issue documented here:

Holman, Kevin. OpsMgr: Network utilization scripts in BaseOS MP version 6.0.6958.0 may cause high CPU utilization and service crashes on Server 2003 (http://blogs.technet.com/b/kevinholman/archive/2011/12/12/opsmgr-network-utilization-scripts-in-baseos-mp-version-6-0-6958-0-may-cause-high-cpu-utilization.aspx) 

Also note that Microsoft now offers NIC teaming as part of Windows Server 2012.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2847767 - Last Review: May 13, 2013 - Revision: 2.0
Applies to
  • Microsoft System Center Operations Manager 2007 R2
Keywords: 
KB2847767

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com