FIX: MSMQ Transactional Messages May Be Lost

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


When an application uses a single transaction object that is shared by several threads, which are all sending messages using the transaction object, a Message Queueing (MSMQ) server or client under stress may lose a transactional message during operation.


This problem is caused by a thread timing issue in the MSMQ Queue Manager.


To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack


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

This problem was first corrected in Windows 2000 Service Pack 1.


Article ID: 254283 - Last Review: February 28, 2014 - Revision: 1.1
  • Microsoft Message Queuing 2.0
kbnosurvey kbarchive kbbug kbfix kbmsmq200fix KB254283

Contact us for more help

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