Microsoft KB Archive/306785

= FIX: Message Queuing messages are not validated with Network Load Balancing =

Article ID: 306785

Article Last Modified on 2/22/2007

-

APPLIES TO


 * Microsoft Message Queuing 2.0
 * Microsoft Message Queuing 3.0

-



This article was previously published under Q306785





SYMPTOMS
When Network Load Balancing redirects a Microsoft Message Queuing message to a server, the server does not accept the message. The message is handled as follows:
 * Express messages are discarded on the receiver.
 * Transactional messages queue up in the outgoing queue of the sender as unacknowledged messages.

If negative acknowledgements (NAK) are requested, and if the time-to-reach-queue timeout expires, a NAK is returned to the sender with the following message class: MQMSG_CLASS_NACK_BAD_DST_Q or &quot;Bad destination&quot;



CAUSE
This behavior occurs because Message Queuing verifies the destination of the message to validate that the message belongs to the Message Queuing server for that computer. When a Message Queuing message that is sent to an NLB netname is redirected to a server behind NLB, the message does not contain the netname of the server to which the message is redirected, and validation fails.



Microsoft Message Queuing 3.0
To resolve this problem, you must add the following registry key:

If this registry key is set to DWORD value 1, Message Queuing does not validate the destination of the message. This permits messages that are sent to an NLB netname to be successfully received by a server behind NLB. If this registry key does not exist or is set to DWORD value 0, Message Queuing validates the server name that is contained in the message to make sure that it matches the name of the server that received the message. You must restart the Message Queuing service after you add or change this registry key.

Note Transactional messaging is still not supported in Message Queuing 3.0. The registry key permits Message Queuing 3.0 to send non-transactional messages over NLB by using Direct=OS format names. Without the registry key, you can only send non-transactional messages over NLB by using Direct=TCP format names.

Hotfix information
Notes:
 * This hotfix applies to the use of Direct=OS format names.
 * Direct=TCP format names are currently supported and do not have this problem.
 * NLB support is limited to non-transactional messages.

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend 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 hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

File information
The English version of this hotfix has the file attributes (or later file attributes) 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 -  29-May-2001    14:22    5.0.0.735     70,000    Mqac.sys 05-Sep-2001   15:59    5.0.0.735    210,000    Mqads.dll 05-Sep-2001   15:59    5.0.0.735     41,000    Mqdssrv.dll 05-Sep-2001   15:59    5.0.0.740    218,000    Mqoa.dll 05-Sep-2001   15:59    5.0.0.741    409,000    Mqqm.dll 05-Sep-2001   15:59    5.0.0.741     90,000    Mqrt.dll 05-Sep-2001   15:59    5.0.0.738     69,000    Mqsec.dll 05-Sep-2001   15:59    5.0.0.738    106,000    Mqutil.dll After you apply this hotfix, you must add the following registry key:

If this registry key is set to DWORD value 1, Message Queuing does not validate the destination of the message. This permits messages that are sent to an NLB netname to be successfully received by a server behind NLB. If this registry key does not exist or is set to DWORD value 0, Message Queuing validates the server name that is contained in the message to make sure that it matches the name of the server that received the message. You must restart the Message Queuing service after you add or change this registry key.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: MSMQ NLB FormatName

Keywords: kbhotfixserver kbqfe kbprb kbqfe KB306785

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.