FIX: Message Queuing messages may accumulate in a transactional queue

This article has been archived. It is offered "as is" and will no longer be updated.
In Microsoft Message Queuing, also known as MSMQ, messages may accumulate in a transactional queue if the following conditions are true:
  • The sender application is multi-threaded, or multiple applications are sending to the same queue.
  • The messages are transactional.
  • The receiving application uses asynchronous or synchronous receives or peeks.

    Note This problem discussed in this article has been identified to occur with the Microsoft Message Queuing Trigger Service.
For additional information about this problem, visit the following Microsoft Web site:
When multiple senders send transactional messages to the same queue, message #n+1 may become available before message #n. If a reader reads from a queue by using a cursor, the reader may skip message #n. If this problem occurs, it may appear that data has been lost. However, what has occurred is that the queue cursor has advanced. Subsequent reads will not retrieve the message that was initially skipped unless you restart Message Queuing.

Hotfix information

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 Message Queuing 2.0 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: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.


You must have Windows 2000 Service Pack 4 installed before you apply this hotfix.

Restart requirement

You must restart Message Queuing after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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   --------------------------------------------------------------   11-May-2004  17:16         291,088  Mq1repl.dll         22-Dec-2003  19:26          14,096  Mq1sync.exe         11-May-2004  12:34          76,944  Mqac.sys   11-May-2004  17:16         217,360  Mqads.dll           20-Sep-2003  16:23          25,360  Mqbkup.exe          11-May-2004  17:16          76,560  Mqdscli.dll         11-May-2004  17:16          42,256  Mqdssrv.dll         22-Dec-2003  19:26          98,064  Mqmig.exe           11-May-2004  17:16         266,512  Mqmigrat.dll        11-May-2004  17:16         222,480  Mqoa.dll            11-May-2004  17:16          10,000  Mqperf.dll          11-May-2004  17:16         436,496  Mqqm.dll            11-May-2004  17:16         102,672  Mqrt.dll            11-May-2004  17:16          70,928  Mqsec.dll           11-May-2004  17:16         400,656  Mqsnap.dll          11-May-2004  17:16          23,824  Mqupgrd.dll         11-May-2004  17:16         110,864  Mqutil.dll          11-May-2004  17:16          64,784  Msmq.cpl
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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

Article ID: 839258 - Last Review: 01/15/2015 16:19:46 - Revision: 5.1

Microsoft Message Queuing 2.0

  • kbnosurvey kbarchive kbbug kbfix kbqfe kbhotfixserver KB839258