Article ID: 828946
Article Last Modified on 10/25/2005
APPLIES TO
- Microsoft Message Queuing 2.0
SYMPTOMS
Messages that are addressed to SPX destination queues that are not valid may appear in the Microsoft Message Queuing Microsoft Management Console (MMC) snap-in. Messages that are correctly addressed may also accumulate in outgoing queues.
CAUSE
This problem occurs if the version of the Mqqm.dll file is greater than 756 and if Message Queuing is installed in Workgroup mode.
As a reference, Windows 2000 Service Pack 3 (SP3) contains build 751 of the Mqqm.dll file and Windows 2000 SP4 contains build 775 of the Mqqm.dll file. This problem is corrected in build 785 of the Mqqm.dll file.
RESOLUTION
Hotfix Information
A 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.
Prerequisites
No prerequisites are required.
Restart Requirement
You must restart your computer after you apply this hotfix.
File Information
The English version of this hotfix has the file attributes (or later) 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 --------------------------------------------------------------------------------------- 03-Oct-2003 16:47 5.0.0.778 281,360 Mq1repl.dll 20-Sep-2003 16:23 5.0.0.778 14,096 Mq1sync.exe 02-Oct-2003 18:21 5.0.0.785 76,016 Mqac.sys 03-Oct-2003 16:47 5.0.0.783 217,360 Mqads.dll 20-Sep-2003 16:23 5.0.0.761 25,360 Mqbkup.exe 03-Oct-2003 16:47 5.0.0.785 76,560 Mqdscli.dll 03-Oct-2003 16:47 5.0.0.773 42,256 Mqdssrv.dll 20-Sep-2003 16:23 5.0.0.759 98,064 Mqmig.exe 03-Oct-2003 16:47 5.0.0.759 265,488 Mqmigrat.dll 03-Oct-2003 16:47 5.0.0.740 222,480 Mqoa.dll 03-Oct-2003 16:47 5.0.0.784 10,000 Mqperf.dll 03-Oct-2003 16:47 5.0.0.785 431,888 Mqqm.dll 03-Oct-2003 16:47 5.0.0.778 102,672 Mqrt.dll 03-Oct-2003 16:47 5.0.0.776 70,928 Mqsec.dll 03-Oct-2003 16:47 5.0.0.783 400,656 Mqsnap.dll 03-Oct-2003 16:47 5.0.0.762 23,824 Mqupgrd.dll 03-Oct-2003 16:47 5.0.0.782 110,864 Mqutil.dll 03-Oct-2003 16:47 5.0.0.748 64,784 Msmq.cpl 03-Oct-2003 17:32 5.3.23.4 640,360 Windows2000-kb828946-x86-enu-symbols.exe 03-Oct-2003 17:34 5.3.23.4 1,057,640 Windows2000-kb828946-x86-enu.exe
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Message Queuing always tries to join a domain when it is restarted. When Message Queuing joins a domain, it creates an msmqConfiguration object in the Active Directory directory service. Message Queuing also changes its own queue manager GUID to be the new GUID of the new msmqConfiguration object. Message Queuing then converts all relevant packets in local message files to reflect the change in the queue manager GUID.
The problem occurs with direct messages. The "user header" in Message Queuing messages contains the GUID of the destination computer. This configuration is true for messages that are sent to public or private format names and for messages that are sent to the local computer with a direct format name. However, for messages that are sent to a remote computer with a direct format name, this field in the user header retains the IP address of the source computer. The destination queue manager must have the IP address to send final acknowledgments for transactional (xact) messages after you restart Message Queuing.
The code that converted the packets overwrites the IP of the source computer with a new GUID of the destination (local) computer. The IP address of the source computer is overwritten when the join domain code runs. When you start Message Queuing, this code runs if the computer is part of a domain and if Message Queuing is installed in Workgroup mode.
When Message Queuing tries to send final acknowledgements, it uses the GUID as an address, and the destination format names that are not correct are used (SPX:80, for example). To work around this problem, when the packets are converted, do not overwrite the source IP address in packets that are received from remote computers with direct format names.
This hotfix also includes code that deals with packets that were already corrupted before you applied the hotfix. The outgoing queues that are created for these packets are paused so that CPU and network resources are not wasted. The user cannot delete these files because the format name is not valid. To clean up corrupted storage, stop any inbound messages, receive all legitimate messages from all queues, and then delete the messages files (*.mq) in the Msmq\Storage directory. The hotfix also includes code that prevents sending order/final acknowledgements to corrupted addresses.
The following entries are logged in the Msmq.log file if Message Queuing error logging is enabled:
0x880> Mon Feb 23 13:47:42 2004: QM Error: qmutil/50, BOOL: 0 0x880> Mon Feb 23 13:47:42 2004: QM Error: qmutil/1789, Point
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
Additional query words: management console Mqqm MSMQ
Keywords: kbbug kbfix kbqfe kbwin2000presp5fix kbhotfixserver KB828946
