Jetstress testing failed. Error: Faulty performance counter paths: \Network Interface(*)\*. Ensure that all the performance counters are working correctly with System Monitor. Error: The specified instance is not present.


I came up with a case last week where the Jetstress test was failing with below error:

Jetstress testing failed. Error: Faulty performance counter paths: \Network Interface(*)\*. Ensure that all the performance counters are working correctly with System Monitor. Error: The specified "object was not found on the computer."

What is Jetstress?

Jetstress is used to verify the performance and stability of a disk subsystem prior to putting an Exchange 2013 or Exchange 2016 server into production. Jetstress helps verify disk performance by simulating Exchange disk Input/Output (I/O) load. Specifically, Jetstress simulates the Exchange database and log file loads produced by a specific number of users. You use Performance Monitor, Event Viewer, and ESEUTIL in conjunction with Jetstress to verify that your disk subsystem meets or exceeds the performance criteria you establish. After a successful completion of the Jetstress Disk Performance and Stress Tests in a non-production environment, you will have ensured that your Exchange disk subsystem is adequately sized (in terms of performance criteria you establish) for the user count and user profiles you have established. It is highly recommended that the Jetstress user read through the tool documentation before using the tool.

You can download the Exchange 2013\2016 Jetstress tool from Here

Based on the error description, we could see there was some issue with Network Interface counter in Perfmon.

We launched the Perfmon from the server and got the below error

"Unable to add these counters:
\Network Interface(*)\Bytes Total/sec"

We ran the following command to query the performance counter service information

lodctr /q

We could see the TCPIP performance counter was disabled.

[Tcpip] Performance Counters (Disabled)
DLL Name: %SystemRoot%\System32\Perfctrs.dll
Open Procedure: OpenTcpIpPerformanceData
Collect Procedure: CollectTcpIpPerformanceData
Close Procedure: CloseTcpIpPerformanceData

We used the following command to enable the TCPIP performance counter
lodctr /e:tcpip

We were now able to run the JetStress without any issue.

Happy Troubleshooting!!!!

-Raghav

Comments (0)

Skip to main content