FIX: Messages Stuck in Outgoing Queue When Remote Queue Is Deleted

Article translations Article translations
Article ID: 279130 - View products that this article applies to.
This article was previously published under Q279130
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

SYMPTOMS

An accumulation of transactional messages in the outgoing queue on the sending computer may occur when only one message is sent to a queue. The MSMQ Queue Performance Monitor counter shows many instances of one message going to one remote queue. This can also occur in the MSMQ snap-in under Computer Management on a computer running Windows 2000. Both the number of messages in the outgoing queue and the number of outgoing queues continue to grow. There is only one message in each outgoing queue.

CAUSE

The transactional acknowledgement that results in the deletion of the message from the outgoing queue is not generated when only one message is sent to the queue.

RESOLUTION

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 fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


The English version of this fix should have the following file attributes or later:
Date        Time    Version      Size    File name       Platform
-----------------------------------------------------------------
1/19/2001   11:04a        720   278,800  Mq1repl.dll          x86
1/16/2001    7:57a        720    14,096  Mq1sync.dll          x86
1/16/2001    7:57a        720    71,408  Mqac.sys             x86
1/19/2001   11:04a        720   214,288  Mqads.dll            x86
1/16/2001    7:57a        720    21,776  Mqbkup.exe           x86
1/19/2001   11:04a        720    29,456  Mqcertui.dll         x86
1/19/2001   11:04a        720    49,424  Mqclus.dll           x86
1/19/2001   11:04a        720    29,968  Mqdbodbc.dll         x86
1/19/2001   11:04a        720    75,536  Mqdscli.dll          x86
1/19/2001   11:04a        720    41,744  Mqdssrv.dll          x86
1/16/2001    7:57a        720    98,064  Mqmig.exe            x86
1/19/2001   11:04a        720   263,952  Mqmigrat.dll         x86
1/19/2001   11:04a        720   223,504  Mqoa.dll             x86
1/19/2001   11:04a        720     7,952  Mqperf.dll           x86
1/19/2001   11:04a        720   413,968  Mqqm.dll             x86
1/19/2001   11:04a        720     8,464  Mqrperf.dll          x86
1/19/2001   11:04a        720    91,920  Mqrt.dll             x86
1/19/2001   11:04a        720    70,416  Mqsec.dll            x86
1/19/2001   11:04a        720   400,144  Mqsnap.dll           x86
1/16/2001    7:57a        720    14,096  Mqsvc.exe            x86
1/19/2001   11:04a        720    24,336  Mqupgrd.dll          x86
1/19/2001   11:04a        720   107,792  Mqutil.dll           x86
1/19/2001   11:04a        720    64,784  Msmq.cpl             x86
1/19/2001   11:04a        720   159,504  Msmqocm.dll          x86
					

STATUS

Microsoft has confirmed that this is a problem in MSMQ version 2.0.

MORE INFORMATION

The order acknowledgement is now generated, even when only one message is sent to the queue.

Steps to Reproduce This Behavior

  1. Create a transactional queue.
  2. Send a transactional message to the queue.
  3. Receive the message from the queue, and then delete the queue.
Result: The message in the outgoing queue on the sending computer is not removed until it expires, which is the Time To Be Received value or the system wide message lifetime (90 days by default).

Properties

Article ID: 279130 - Last Review: February 28, 2014 - Revision: 1.4
APPLIES TO
  • Microsoft Message Queuing 2.0
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB279130

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com