• Article

Performance data is not collected

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at https://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2011-07-29

When you run the Microsoft Exchange Performance Troubleshooter on a Windows Server 2008-based computer that has Microsoft Exchange Server installed, the tool cannot gather or analyze performance data. In this scenario, the tool generates one or more of the following error messages:

The version of the operating system on the server ServerName is later than that on the local computer. Data collection and analysis may not work from the local machine.

Failed to read performance data. Unable to read performance data from the file FileName.

An error occurred while retrieving local directory information. Please make sure you have provided valid credentials.

Failed to find ExMon file locally.

Failed to find the Exmon file.

This issue occurs because earlier versions of the Exchange Performance Troubleshooter are not cluster aware.

Exchange Performance Troubleshooter collects Exchange performance data by using Logman, which manages the Performance Logs and Alerts service on the Exchange server.  Exchange Performance Troubleshooter copies the data from the Exchange server to the local computer.  To do this, it copies from a UNC share, which is usually the Exchange server name (\\servername\c$\perfdata). However, when you run the Exchange Performance Troubleshooter in a clustered Exchange environment, you must consider the following:

  • When running Exchange Performance Troubleshooter on a Windows Server 2003 cluster, you must use the Central Management Server (CMS) node name as the UNC name.

  • When running Exchange Performance Troubleshooter on a Windows Server 2008 cluster, you must use the Exchange Virtual Server (EVS) name as the UNC name.

  • When running Exchange Performance Troubleshooter on a Windows Server 2003-based computer, you cannot remotely view the CMS cluster information on a Windows Server 2003 cluster. In this case, you must run the tool on the local Windows Server 2003 cluster node.

  • When running Exchange Performance Troubleshooter on a Windows Server 2008-based computer or cluster, you can remotely view the CMS information on another Windows Server 2008 cluster. However, you cannot view the CMS information on a Windows Server 2003 cluster.