Microsoft KB Archive/884975

= Performance Monitor counters may not appear, and the counter values may be incorrect when you remotely monitor clustered instances of Message Queuing in Windows 2000 Server =

Article ID: 884975

Article Last Modified on 1/4/2006

-

APPLIES TO


 * Microsoft Message Queuing 2.0
 * Microsoft Windows 2000 Advanced Server

-





Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
When you try to remotely monitor a clustered instance of Microsoft Message Queuing (also known as MSMQ), you may experience the following problems:
 * The Message Queuing Performance Monitor (Perfmon) counters appear only if the local node Message Queuing service is started.
 * The values of the counters for clustered instances of Message Queuing are incorrect.
 * The Perfmon counters for clustered queues do not appear.



CAUSE
These problems occur because of the changes that were made in Microsoft Windows 2000 Server Service Pack 4 (SP4). The problems also occur because of changes in hotfixes that were released after Windows 2000 Server SP3.

The service pack and hotfixes install Mqperf.dll version 5.0.0.762 or a later version. The updates have changed the way Message Queuing Perfmon counters are loaded. The Remote Registry Service that loads the Perfmon counters is not cluster-aware. Therefore, the service does not load values for the clustered Message Queuing Perfmon counters. Instead, the service loads the values of the local-node Message Queuing service.



WORKAROUND
To work around these problems, use one of the following methods:  Run Perfmon from a clustered command prompt. To do this, follow these steps:  On the computer that owns the cluster, click Start, point to Programs, point to Administrative Tools, and then click Cluster Administrator. Click the Groups folder. In the details pane, click the cluster group that you want the resources for Message Queuing to belong to. On the File menu, point to New, and then click Resource. In the New Resource Wizard, click Generic Application in the Resource Type list, and then click Next.</li> On the Possible Owners page, make sure that all the nodes in the cluster are listed under Possible Owners, and then click Next.</li> On the Dependencies page, click Network Name in the Available resources list, and then click Next.</li> On the Generic Application Parameters page, type Cmd.exe in the Command line box.</li> In the Current Directory box, type the following path. C:\WINNT is the folder where Windows is installed:

C:\WINNT \System32

</li> Click to select the Allow application to interact with desktop check box and the Use Network Name for computer name check box, and then click Next.</li> On the Registry Replication page, click Finish. Do not add any registry keys.</li> Click the Resources folder. In the details pane, click the resource that you just created.</li> On the File menu, click Bring Online.</li></ol> </li> Use the MSMQ Local Admin API to write your own performance monitoring application to remotely monitor the cluster’s Perfmon counters.</li> Do not install any Message Queuing hotfixes that include Mqperf.dll version 5.0.0.762 or a later version and that are dated November 12, 2002.</li> Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To monitor only one clustered instance of Message Queuing, add the following registry subkey:

To add the registry subkey, follow these steps: <ol> Click Start, type regedit, and then click OK.</li> In Registry Editor, locate the following registry subkey:

</li> Right-click Parameters, point to New, and then click String Value.</li> In the right pane, replace &quot;New Value&quot; with. is the network name of the clustered instance of Message Queuing that you want to monitor. Type the name in all uppercase letters.</li></ol>

After you have added the registry subkey, you must restart Message Queuing.

Notes <ul> <li>You can monitor the specified clustered Message Queuing instance from any computer. This includes remote computers. However, you cannot monitor any other instances of Message Queuing that may be running on your cluster.</li> <li>This registry subkey requires that you apply the hotfix that is described in Microsoft Knowledge Base article 267316. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

267316 FIX: Performance monitor counters are lost on the cluster during failover in Message Queuing

</li></ul> </li></ul>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in Windows 2000 Server SP4 and some hotfixes that were released after Windows 2000 Server SP3.

<div class="references_section">