When running tests you receive the following error: "Failed to retrieve performance counter"
Example Error:
PhysicalDisk/Avg. Disk sec/Read(2 E:)
Failed to retrieve performance counter.
Instance is currently not available
The specified instance may not be currently active. Verify that the process that starts the object counter is installed and started on the server.
Steps to try and resolve this issue.
Make sure the credentials used to run the test are a member of the local administrators group on the target server.
Check to make sure you can connect to the target server from the Spotlight On Messaging Server using perfmon.
If you can't connect to the target server using perfmon there could be a firewall blocking access.
From the Spotlight on Messaging server open perfmon and connect to the target server and the instance of perfmon counter described in the error details. If the perfmon object is not displayed there could be a problem with the perfmon library on the target server.
You can also try to log on to the target server and run perfmon locally and try to connect to the perfmon object. If the perfmon object is not displayed when logged on locally the performance counter libraries may have been corrupted. Refer to the Microsoft KB article ID 300956 - "How to manually rebuild Performance Counter Library values" to rebuild the Exchange server Performance counter libraries.
http://support.microsoft.com/kb/300956
Notes:
If you have manually added counters in your health test that refer to a specific perfmon Object/Instance then the server is reconfigured and that Object\Instance is no longer on the server you will need to edit your test and remove the manually added counter.
If you are running tests against Exchange 2010 SP1, Spotlight on Messaging 7.4.1 and previous versions do not support Exchange 2010 SP1. Support for Exchange 2010 SP1 is included in Spotlight on Messaging 7.5 and greater.
Also if the counter is not available due to a component of Exchange not being installed on the Exchange Server you can edit your test and delete the counter or change the server role that should check this counter.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy