A message may be lost, and Message Queuing may stop responding when a message is moved to the transactional dead-letter queue in Message Queuing (820951)



The information in this article applies to:

  • Microsoft Message Queuing 2.0

SYMPTOMS

When a message is moved to the transactional dead-letter queue in a Microsoft Message Queuing enterprise, you may experience one of the following symptoms:
  • The message may be lost if Message Queuing stops responding before the receive operation is committed.
  • Message Queuing may stop responding during the next transactional send operation.

CAUSE

This issue occurs if a transactional receive operation is pending on an empty transactional dead-letter queue.

RESOLUTION

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 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: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 fix 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 
-----------------------------------------------------------------
30-Jul-2003 	10:32 	5.0.0.778 	281,360 	Mq1repl.dll 
17-Jun-2003 	09:33 	5.0.0.778 	 14,096 	Mq1sync.exe 
30-Jul-2003 	10:19 	5.0.0.781 	 76,144 	Mqac.sys
30-Jul-2003 	10:32 	5.0.0.773 	217,360 	Mqads.dll 
30-Oct-2002 	08:43	5.0.0.761 	 25,360 	Mqbkup.exe 
30-Jul-2003 	10:32 	5.0.0.778 	 76,560 	Mqdscli.dll
30-Jul-2003 	10:32 	5.0.0.773 	 42,256 	Mqdssrv.dll 
21-Oct-2002 	12:31	5.0.0.759 	 98,064 	Mqmig.exe 
30-Jul-2003 	10:32 	5.0.0.759 	265,488		Mqmigrat.dll 
30-Jul-2003 	10:32 	5.0.0.740 	222,480 	Mqoa.dll 
30-Jul-2003 	10:32 	5.0.0.762 	  8,464 	Mqperf.dll 
30-Jul-2003 	10:32 	5.0.0.780 	428,816		Mqqm.dll 
30-Jul-2003 	10:32 	5.0.0.778 	102,672 	Mqrt.dll 
30-Jul-2003	10:32 	5.0.0.776 	 70,928 	Mqsec.dll 
30-Jul-2003 	10:32 	5.0.0.781 	400,656		Mqsnap.dll 
30-Jul-2003 	10:32 	5.0.0.762 	 23,824 	Mqupgrd.dll 
30-Jul-2003	10:32 	5.0.0.778 	110,864 	Mqutil.dll 
30-Jul-2003 	10:32 	5.0.0.748 	 64,784		Msmq.cpl 

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

REFERENCES

For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New naming schema for Microsoft Windows hotfix packages


Modification Type:MinorLast Reviewed:10/5/2005
Keywords:kbBug kbfix kbQFE kbWin2000preSP5fix KB820951 kbAudITPRO