Consider the following scenario:
Additionally, the following error may be logged in the Application Event Log after each query.
Log Name: Application
Source: Microsoft-Windows-PerfNet
Date: 3/30/201 10:15:29 AM
Event ID: 2006
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <computer name>
Description:Unable to read Server Queue performance data from the Server service. The first four bytes (DWORD) of the Data section contains the status code, the second four bytes contains the IOSB.Status and the next four bytes contains the IOSB.Information.Unable to read Server Queue performance data from the Server service. The first four bytes (DWORD) of the Data section contains the status code, the second four bytes contains the IOSB.Status and the next four bytes contains the IOSB.Information.
- Windows Server 2008 R2 installed on a machine with more than 64 logical processors
- An application uses Windows Management Instrumentation (WMI) to query performance data related to logical processors (the following WMI class is an example: Win32_PerfFormattedData_PerfOS_Processor.)
Additionally, the following error may be logged in the Application Event Log after each query.
Log Name: Application
Source: Microsoft-Windows-PerfNet
Date: 3/30/201 10:15:29 AM
Event ID: 2006
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <computer name>
Description:Unable to read Server Queue performance data from the Server service. The first four bytes (DWORD) of the Data section contains the status code, the second four bytes contains the IOSB.Status and the next four bytes contains the IOSB.Information.Unable to read Server Queue performance data from the Server service. The first four bytes (DWORD) of the Data section contains the status code, the second four bytes contains the IOSB.Status and the next four bytes contains the IOSB.Information.