Article ID: 237541 - View products that this article applies to.
This article was previously published under Q237541
This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft Exchange Server Performance Monitor counters may not be available after the Exchange Server services have moved to the second node of a Windows NT cluster. The counters may not be available using the Exchange Server virtual name or the actual computer name when you select the computer in Performance Monitor.
The behavior occurs when the order of software installed on the Cluster Server nodes is different. The performance key for each of the Exchange Server services contains the index in the HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Perflib\009\Counters registry key, where the first and last counters for the Exchange Server services exist. If you install software into a cluster in a different order, the values for each service are different for each server in the cluster. The registry replication in a cluster is currently set to replicate all subkeys for the particular service key, including the performance key. This overwrites the values of one server with the values of another server in the cluster. Hence, the values in the Counters key on the second node no longer match the indices in performance keys of the services.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMSNOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Component: Setup Program
Collapse this tableExpand this table
After you obtain the fix, follow these steps to apply it:
The available fix only corrects the behavior on new installations of Exchange Server into a cluster environment. If you have already installed Exchange Server, perform the following steps to manually correct the behavior:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Article ID: 237541 - Last Review: October 21, 2013 - Revision: 3.3