MSMQ Cluster

On any MSMQ server, it’s usually a good idea to implement the BindInterfaceIP key if there are multiple NICs involved, especially if there are multiple IPs which map to different subnets. MSMQ will pick one, and then use the subnet from that IP to determine its site membership. On a cluster, you almost always have the clustered IP, and the IP from the heartbeat NIC which can cause problems, so it’s especially important to include this key on a cluster. Here’s the reference:

329492 A cluster node with two network cards does not receive messages

http://support.microsoft.com/default.aspx?scid=kb;EN-US;329492

We also recommend using MMCV to view the queues, and keeping TMQ handy:

898701 How to use the Mmcv.exe utility to manage clustered Message Queuing resources

http://support.microsoft.com/default.aspx?scid=kb;EN-US;898701

887220 Description of TMQTools utilities for Microsoft Message Queuing

http://support.microsoft.com/default.aspx?scid=kb;EN-US;887220

You had also asked about getting performance counters to work on an MSMQ cluster. As we discussed, on a typical MSMQ cluster, there are at least 3 instances of MSMQ, the clustered instance, and the two local instances. Only one instance can be monitored remotely. You need to add the NetNameForPerfCounters registry key as described in this article:

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

http://support.microsoft.com/default.aspx?scid=kb;EN-US;884975

The key should be added to both nodes, and if you’re still having problems, to the clustered registry section of MSMQ as well (Clustered QMs\MSMQ$MyResource\Parameters). The computer should then be rebooted. When adding the key, please note that the machine name needs to be added in uppercase letters. If the counters are still not visible remotely, then try the following:

-From a clustered command prompt, run “perfmon” and see if they’re viewable. If they are, then we know the MSMQ counters are working, and we’re having problems with the key. Try restarting the remote registry service on the active node, and see if that resolves the problem of viewing the counters remotely.

-If the counters are still not viewable, remove the registry key, and start the local MSMQ service on the inactive node, see if you can view the counters

-If the counters are not viewable from a clustered command prompt, then most likely there’s a problem with the counters themselves. Run the following command from a regular command prompt on both nodes:

-unlodctr MSMQ

-Reboot

-Switch to the Windows\System32 directory

-lodctr mqperf.ini

-Reboot

-Test the counters