Microsoft KB Archive/898618

= FIX: Transactional messages that are addressed to a nonexistent queue remain in the outgoing queue in Message Queuing 3.0 =

Article ID: 898618

Article Last Modified on 3/23/2007

-

APPLIES TO


 * Microsoft Message Queuing 3.0
 * Microsoft BizTalk Adapter for MSMQ 2.0

-





SYMPTOMS
In Microsoft Message Queuing (also known as MSMQ) 3.0, transactional messages that are addressed to a nonexistent queue remain in the outgoing queue. You expect these transactional messages to go to the dead-letter queue.



Service pack information
To 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:

889100 How to obtain the latest service pack for Windows Server 2003

Prerequisites
No prerequisites are required.

Restart requirement
You do not have to restart the computer after you apply this hotfix.

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.

Windows Server 2003 x64 Edition


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in Windows Server 2003 Service Pack 2.



MORE INFORMATION
In Message Queuing 3.0, the response to a BAD_DST_Q_NACK acknowledgement was changed. This change was made to handle the situation where a queue is created in the Active Directory directory service but has not yet replicated to the destination computer where the actual queue will reside. Because the messages remain in the outgoing queue, the messages are sent when the queue replicates to the destination computer.

This change also causes problems to occur with the BizTalk Message Queuing Adapter (MSMQT) in Microsoft BizTalk Server. When messages are sent to MSMQT and the queue does not have an associated subscriber, MSMQT issues a BAD_DST_Q_NACK acknowledgement. The Message Queuing 3.0 sender keeps the messages in the outgoing queue and keeps trying to send the messages.

