Message Queuing does not detect the logical end of a message chain when you use an MQSeries correlation ID to link messages (327162)
The information in this article applies to:
- Microsoft Message Queuing 2.0
This article was previously published under Q327162 Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry SYMPTOMSWhen you use an MQSeries correlation ID to link messages in Microsoft Message Queuing, Message Queuing does not detect the logical end of the message chain.CAUSEThis problem occurs if you configure the 24-byte MQSeries correlation ID as a series of 24 instances of hexadecimal zero. Message Queuing will implement the MQSeries correlation ID as "FQ2Q" followed by a series of 20 instances of hexadecimal zero. RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem. To resolve this problem, 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 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
--------------------------------------------------------
06-Aug-2002 14:18 5.64.0.846 37,136 Bcluster.exe
06-Aug-2002 14:18 5.64.0.846 340,240 Explres.dll
06-Aug-2002 14:18 5.64.0.846 65,808 Mqbinst.dll
05-Dec-2001 16:07 4,608 Mqfrgnky.dll
06-Aug-2002 14:18 157,756 Msimqbsetup.lib
06-Aug-2002 14:18 5.64.0.846 274,704 Q2qcldll.dll
06-Aug-2002 14:18 5.64.0.846 819,472 Q2qexpl.exe
06-Aug-2002 14:18 5.64.0.846 889,104 Q2qgw.exe
06-Aug-2002 14:18 5.64.0.846 33,040 Q2qmsg.dll
05-Dec-2001 16:07 3,817 Q2qperf.ini
06-Aug-2002 14:18 5.64.0.846 348,432 Q2qprfdl.dll
05-Dec-2001 16:07 686 Q2qprfsm.def
06-Aug-2002 14:18 5.64.0.846 327,952 Q2qshdll.dll
06-Aug-2002 14:18 5.64.0.846 41,232 Shdllres.dll
06-Aug-2002 14:18 5.64.0.846 90,384 Wmimqbridge.dll
05-Dec-2001 15:59 6,403 Wmimqbridge.mof
STATUSMicrosoft 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 file naming schema for Microsoft Windows software update packages
Modification Type: | Minor | Last Reviewed: | 10/18/2005 |
---|
Keywords: | kbWin2000preSP5fix kbQFE kbbug kbfix KB327162 kbAudITPRO |
---|
|