Article ID: 267316 - View products that this article applies to.
This article was previously published under Q267316
This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows Registry
Microsoft Message Queuing, also known as MSMQ, may report information that is not correct in Performance Monitor (Perfmon). This problem occurs with Message Queuing on a Microsoft Windows 2000 cluster and on a Microsoft Windows Server 2003 cluster. Message Queuing may also lose Perfmon counters after a failover between nodes.
The following error message may be logged in the application event log:
Message Queuing Performance Monitor counter data is exchanged between Message Queuing and Mqperf.dll, the Message Queuing Performance Monitor DLL. The data is exchanged in shared memory. Multiple service instances on a computer, such as when Message Queuing is running on the local node and on the virtual server on the cluster, all write performance data to the same location in memory. This makes the performance results meaningless.
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 05-Sep-2003 18:46 126.96.36.1998 281,360 Mq1repl.dll 17-Jun-2003 15:33 188.8.131.528 14,096 Mq1sync.exe 28-Aug-2003 16:00 184.108.40.2063 76,144 Mqac.sys 05-Sep-2003 18:46 220.127.116.113 217,360 Mqads.dll 30-Oct-2002 14:43 18.104.22.1681 25,360 Mqbkup.exe 05-Sep-2003 18:46 22.214.171.1248 76,560 Mqdscli.dll 05-Sep-2003 18:46 126.96.36.1993 42,256 Mqdssrv.dll 21-Oct-2002 18:31 188.8.131.529 98,064 Mqmig.exe 05-Sep-2003 18:46 184.108.40.2069 265,488 Mqmigrat.dll 05-Sep-2003 18:46 220.127.116.110 222,480 Mqoa.dll 05-Sep-2003 18:46 18.104.22.1684 10,000 Mqperf.dll 05-Sep-2003 18:46 22.214.171.1243 431,888 Mqqm.dll 05-Sep-2003 18:46 126.96.36.1998 102,672 Mqrt.dll 05-Sep-2003 18:46 188.8.131.526 70,928 Mqsec.dll 05-Sep-2003 18:46 184.108.40.2063 400,656 Mqsnap.dll 05-Sep-2003 18:46 220.127.116.112 23,824 Mqupgrd.dll 05-Sep-2003 18:46 18.104.22.1682 110,864 Mqutil.dll 05-Sep-2003 18:46 22.214.171.1248 64,784 Msmq.cpl
Service pack informationTo resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/889100/ )How to obtain the latest service pack for Windows Server 2003
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
This hotfix has an important limitation. After you apply this hotfix, you can no longer view Performance Monitor counters for clustered queues from remote computers. This includes the local cluster nodes. This limitation also exists in Windows 2000 Service Pack 4 (SP4) and in Windows Server 2003.
The underlying reason for this limitation is that this hotfix permits different instances of Message Queuing to store performance data in separate spaces in memory. Each memory space is labeled with the computer name of its corresponding instance of Message Queuing. This is typically the name of the computer, except in a cluster. In a cluster, the name is the network name of the virtual Cluster service. The Message Queuing Performance Monitor DLL, Mqperf.dll, queries for the name of the local computer and then uses the name of the local computer to determine the set of performance data to read.
This always works correctly when an application accesses the counters for the computer where the application runs, whether that computer is a stand-alone computer, a cluster node computer, or a virtual Cluster service computer. In this case, Mqperf.dll is loaded directly by the application. Therefore, when Mqperf.dll queries for the name of the local computer, Mqperf.dll receives the correct name back.
Problems only occur when you try to access the counters for a remote computer. In this case, Mqperf.dll is loaded by the remote registry service. The remote registry service works as expected on a stand-alone computer, but the remote registry service is not cluster-aware. Therefore, on a cluster node, the remote registry service always runs locally. In this situation, when Mqperf.dll queries for the name of the local computer, the remote registry service always receives the name of the local cluster node and not the names of any one of the virtual Cluster services. Therefore, you can correctly view the Performance Monitor counters for the local cluster nodes from remote computers. However, you cannot view the counters for the virtual Cluster services that are running on those nodes. This problem occurs even when you specify a virtual Cluster service name when you open the counters. The local cluster nodes are considered "remote" to the virtual Cluster service as far as Message Queuing is concerned. Therefore, you cannot even view the clustered counters from the local nodes of the cluster.
There are three possible workarounds for this problem:
Article ID: 267316 - Last Review: February 28, 2014 - Revision: 10.0