Messages from clustered Message Queuing Resource Service do not arrive at destination (311827)



The information in this article applies to:

  • Microsoft Message Queuing 2.0

This article was previously published under Q311827
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 send transacted messages from a clustered Microsoft Message Queuing Resource Service by using Direct= ... syntax in the FormatName property, the messages may remain in the sender computer and may not arrive at the destination. Specifically, the connection is established but the messages are not delivered.

When you send direct or transacted messages from a remote (noncluster) computer to the same queue, the operation is successful. When you send from the same clustered Message Queuing Resource Service to the same queue by using syntax other than Direct= ... in the FormatName property, this operation is also successful.

CAUSE

When a client performs a broadcast to resolve its site and connected network, a Microsoft Message Queuing, also known as MSMQ, computer on a cluster may answer it by using the node's IP address; as a result, the answer does not reach the client. The client may fail to bind remote procedure call (RPC) listening ports to the necessary IP addresses, and therefore it does not accept messages from those addresses.

RESOLUTION

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.
This hotfix adds a new registry subkey of type REG_DWORD:

HKEY_LOCAL_MACHINE\Software\Microsoft\MSMQ\Parameters\StaticAddrRes

If the value of this subkey is set to 0 or does not exist, the client broadcasts when it connects through Remote Access Service (RAS) or whenever its IP address is changed. However, if this subkey is set to a non-zero value, the client never broadcasts and it assumes that its connected network and site remain static. It then uses the current registry values for this information.

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. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, 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:NOTE: 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English-language version of this fix should have the following file attributes or later:
   Date        Time    Version       Size    File name     Platform
   -------------------------------------------------------------
   05/19/2001  03:15p  5.0.0.735     71,120  mqac.sys      x86
   05/19/2001  03:23p  5.0.0.721     214,288 mqads.dll     x86
   05/19/2001  03:23p  5.0.0.720     41,744  mqdssrv.dll   x86
   05/19/2001  03:23p  5.0.0.734     414,992 mqqm.dll      x86
   05/19/2001  03:23p  5.0.0.733     91,920  mqrt.dll      x86
   01/15/2001  10:39a  5.0.2195.3140 3,584   spmsg.dll     x86
				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:10/6/2005
Keywords:kbprb kbQFE KB311827