Performance Counter Status

Applies To: Windows Server 2008

Performance Counters are collected and used by services and applications. If they are installed incorrectly or with improper permissions, or if required files are not enabled on the system, those services or applications cannot collect or interpret the data.

Events

Event ID	Source	Message
1900	Microsoft-Windows-PerfCtrs	An extensible counter opened the Event Log for PERFCTRS.DLL
1999	Microsoft-Windows-PerfCtrs	An extensible counter closed the Event Log for PERFCTRS.DLL
2000	Microsoft-Windows-PerfCtrs	Entered the OpenTDIPerformanceData routine.
2001	Microsoft-Windows-PerfCtrs	Unable to open TDI device for RW access. Returning IO Status Block in Data.
2002	Microsoft-Windows-PerfCtrs	Opened TDI device for RW access.
2003	Microsoft-Windows-PerfCtrs	Unable to allocate memory for TDI Information block. Close one or more applications and retry.
2004	Microsoft-Windows-PerfCtrs	Error requesting data from Device IO Control. Returning IO Status Block.
2005	Microsoft-Windows-PerfCtrs	Unable to read data from the TDI device.
2006	Microsoft-Windows-PerfCtrs	Data received from Device IO Control. Returning IO Status Block.
2007	Microsoft-Windows-PerfCtrs	Unable to allocate memory for TDI Statistics block. Close one or more applications and retry.
2099	Microsoft-Windows-PerfCtrs	Successfully completed the TDIOpenPerformanceData routine.
2100	Microsoft-Windows-PerfCtrs	Entered the TDICollectPerformanceData routine.
2101	Microsoft-Windows-PerfCtrs	A Null TDI device handle was encountered in the Collect routine. The TDI file was probably not opened in the Open routine.
2102	Microsoft-Windows-PerfCtrs	The TDI Collection routine ignored a request for data from a foreign computer.
2103	Microsoft-Windows-PerfCtrs	The TDI Collection routine received a request for a counter object that it does not support.
2104	Microsoft-Windows-PerfCtrs	The request for data from the TDI Device IO Control failed. Returning the IO Status Block.
2105	Microsoft-Windows-PerfCtrs	Successful data request from the TDI device.
2106	Microsoft-Windows-PerfCtrs	The buffer passed to CollectTDIPerformanceData was too small to receive the data. No data was returned. The message data shows the available and the required buffer size.
2107	Microsoft-Windows-PerfCtrs	The buffer passed was large enough for the counter data. The counters will now be loaded.
2199	Microsoft-Windows-PerfCtrs	The CollectTDIPerformanceData routine successfully completed.
2200	Microsoft-Windows-PerfCtrs	Entered the CloseTDIPerformanceData routine.
2202	Microsoft-Windows-PerfCtrs	Successfully released the Provider Stats data block.
2203	Microsoft-Windows-PerfCtrs	No SPX Devices are currently open or the NWLink SPX/SPXII service has not been started. SPX performance data cannot be collected.
3000	Microsoft-Windows-PerfCtrs	Entered the OpenNbtPerformanceData routine.
3099	Microsoft-Windows-PerfCtrs	The OpenNbtPerformanceData routine successfully completed.
3100	Microsoft-Windows-PerfCtrs	Entered the CollectNbtPerformanceData routine.
3101	Microsoft-Windows-PerfCtrs	Unable to read IO control information from an NBT device. A network device using the NBT protocol could not be queried.
3102	Microsoft-Windows-PerfCtrs	Successfully read the NBT device IO Control information.
3103	Microsoft-Windows-PerfCtrs	The data buffer passed to the collection routine was too small to receive the data from the NBT device. No data was returned to the caller. The bytes available and the bytes required are in the message data.
3199	Microsoft-Windows-PerfCtrs	The CollectNbtPerformanceData routine successfully completed.
3200	Microsoft-Windows-PerfCtrs	Entered the CloseNbtPerformanceData routine.
4000	Microsoft-Windows-PerfCtrs	Entered the OpenTcpIpPerformanceData routine.
4001	Microsoft-Windows-PerfCtrs	NBT Open failed. See NBT error message.
4002	Microsoft-Windows-PerfCtrs	NBT Open succeeded.
4003	Microsoft-Windows-PerfCtrs	DSIS open failed. See DSIS error message
4004	Microsoft-Windows-PerfCtrs	DSIS Open succeeded.
4005	Microsoft-Windows-PerfCtrs	Failed to load INETMIB1.DLL. Make sure the PATH environment variable contains the DLL. The WIN32 error number is returned in the data.
4006	Microsoft-Windows-PerfCtrs	Unable to look up the address of the SnmpMgrStrToOid routine in the MGMTAPI.DLL library. The WIN32 error number is returned in the data.
4007	Microsoft-Windows-PerfCtrs	Unable to look up the address of an SNMP Extension routine in the INETMIB1.DLL library. The WIN32 error number is returned in the data.
4008	Microsoft-Windows-PerfCtrs	Unable to look up the ID of this object in MIB. Check that the MIB.BIN file is correct.
4009	Microsoft-Windows-PerfCtrs	Initialized the TCP data bindings array.
4010	Microsoft-Windows-PerfCtrs	Unable to get the local computer name. The data in the data section contains the error code.
4011	Microsoft-Windows-PerfCtrs	Unable to open the Snmp Mgr interface for the specified computer. The data contains the error code.
4099	Microsoft-Windows-PerfCtrs	The OpenTcpIpPerformanceData routine successfully completed.
4100	Microsoft-Windows-PerfCtrs	Entered the CollectTcpIpPerformanceData routine.
4101	Microsoft-Windows-PerfCtrs	Received a request for data from a DSIS foreign computer.
4102	Microsoft-Windows-PerfCtrs	The CollectDsisPerformanceData routine returned an error.
4103	Microsoft-Windows-PerfCtrs	The foreign computer did not return any objects.
4104	Microsoft-Windows-PerfCtrs	Successfully retrieved information from the foriegn computer.
4105	Microsoft-Windows-PerfCtrs	The CollectNbtPerformanceData routine returned an error. The error status is in the data section.
4106	Microsoft-Windows-PerfCtrs	The OpenTcpIpPerformanceData routine did not establish a SNMP Mgr Session.
4107	Microsoft-Windows-PerfCtrs	Insufficient memory was available to allocate an SNMP request buffer.
4108	Microsoft-Windows-PerfCtrs	The SnmpMgrRequest call requesting the TCP, IP, UDP and Interface Counters returned an error. The ErrorStatus and ErrorIndex values are shown in Data.
4110	Microsoft-Windows-PerfCtrs	The SnmpMgrRequest call requesting ICMP Counters returned an error. The ErrorStatus and ErrorIndex values are shown in Data.
4111	Microsoft-Windows-PerfCtrs	Processing NetInterface entries.
4112	Microsoft-Windows-PerfCtrs	The buffer is not large enough to store the Network Interface data. The returned data contains the available and required buffer size.
4113	Microsoft-Windows-PerfCtrs	The SnmpGet (GETNEXT) request returned an error while processing the Net Interface instances. The ErrorStatus and ErrorIndex are shown in Data.
4114	Microsoft-Windows-PerfCtrs	Copying data from network requests to the Performance Monitor buffer.
4116	Microsoft-Windows-PerfCtrs	The buffer is not large enough to store the Network Protocol (IP, ICMP, TCP & UDP) data. The returned data contains the available and required buffer size.
4119	Microsoft-Windows-PerfCtrs	SNMP returned a NULL ICMP data buffer. This may be caused by a problem with the SNMP service.
4120	Microsoft-Windows-PerfCtrs	SNMP returned a NULL TCP data buffer. This may be caused by a problem with the SNMP service.
4121	Microsoft-Windows-PerfCtrs	SNMP returned a NULL buffer in response to a request for network performance information. This error may be caused by a problem with the SNMP service.
4199	Microsoft-Windows-PerfCtrs	The CollectTcpIpPerformanceData routine successfully completed.
4200	Microsoft-Windows-PerfCtrs	Entered the CloseTcpIpPerformanceData routine.
4201	Microsoft-Windows-PerfCtrs	SNMP returned an error while trying to close the session.
5300	Microsoft-Windows-PerfCtrs	Entered the OpenDhcpPerformanceData routine.
5301	Microsoft-Windows-PerfCtrs	The OpenDhcpPerformanceData routine successfully completed.
5302	Microsoft-Windows-PerfCtrs	The OpenDhcpPerformanceData routine failed.
5303	Microsoft-Windows-PerfCtrs	Entered the CollectDhcpPerformanceData routine.
5304	Microsoft-Windows-PerfCtrs	The CollectDhcpPerformance routine returned ERROR_MORE_DATA.
5305	Microsoft-Windows-PerfCtrs	The CollectDhcpPerformance routine failed because a shared memory segment was not created.
5306	Microsoft-Windows-PerfCtrs	The CollectDhcpPerformanceData routine completed successfully.
5307	Microsoft-Windows-PerfCtrs	Called the CloseDhcpPerformanceData routine.
5308	Microsoft-Windows-PerfCtrs	The performance counters for the DHCP service have not been installed. No DHCP performance data will be available.

Related Management Information

Windows Performance Counters

Management Infrastructure