Health Monitor Messages in Server Status: "NetworkInterface : Critical Condition. WMI Status:2147749889" (329641)
The information in this article applies to:
- Microsoft Small Business Server 2000
- Microsoft Small Business Server 2000 SP1
This article was previously published under Q329641 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
You may receive the following Health Monitor messages in the Server Status (BackOffice Home) snap-in that is located in the Small Business Server (SBS) 2000 and SBS 2000 Service Pack 1 (SP1) Administrator console:
Severity: Critical
Data Collector: NetworkInterface
Threshold: Bytes Total/sec > 500000
Alert: NetworkInterface:Critical condition.WMI status:2147749889
Severity: Critical
Data Collector: NetworkInterface
Threshold: Error Code (from WMI)
Alert: NetworkInterface:Critical condition.WMI status:2147749889
Additionally, you may receive the following error message in the Health Monitor:
Property: Error Description (from WMI)
Current: Enumeration failed. Object not found. Data Collector is misconfigured.
Property: Error Code (from WMI)
Current: 2147749889
To locate the specific Health Monitor messages, expand the object tree of Health Monitor in the SBS Administrator console, expand All Monitors Computers, expand ServerName, expand Health Monitor Sample Monitors, expand Windows 2000 Performance Monitors, expand Network, expand NetworkInterface, and then on the right side panel, click the Statistics tab. The error details are described in a variety of columns.
CAUSE
This behavior may occur if either the TCP/IP performance counters are turned off or the TCP/IP performance registry keys are missing or corrupted.
RESOLUTIONWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk.
If the performance counters are turned off, you can turn them on by using the following steps:
- Start Registry Editor.
- Locate the Disable Performance Counters value in the following registry location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Performance - On the Edit menu, click DWORD, type 0, and then click OK.
- Quit Registry Editor.
- Restart the server.
If the key mentioned in step 2 is missing, re-create the key. To do so:
- Start Registry Editor.
- Click the TCPIP key in the following registry location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip - On the Edit menu, click Add Key, type Performance for the key name, leave the Class value blank, and then click OK.
- Locate and then click the Performance key in the following registry location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Performance - On the Edit menu, click Add Value, and then add the following registry values:
Value name: Close
Data type: REG_SZ
Value data: CloseTcpIpPerformanceData
Value name: Collect
Data type: REG_SZ
Value data: CollectTcpIpPerformanceData
Value name: Library
Data type: REG_SZ
Value data: Perfctrs.dll
Value name: Open
Data type: REG_SZ
Value data: OpenTcpIpPerformanceData
Value name: WbemAdapFileSize
Data type: REG_DWORD
Radix: Hexadecimal
Value data: a310
Value name: WbemAdapFileTime
Data type: REG_BINARY
Value data: 00a013eca131c201
Value name: WbemAdapFileStatus
Data type: REG_DWORD
Radix: Hexadecimal
Value data: 0
- Save changes, and then quit Registry Editor.
- Restart the server.
STATUSThis behavior is by design.REFERENCES300956 How to Manually Rebuild Performance Counter Library Values
| Modification Type: | Major | Last Reviewed: | 10/13/2002 |
|---|
| Keywords: | kberrmsg kbprb KB329641 |
|---|
|