When you try to send a message by using Microsoft Message Queuing Transport, also known as MSMQT, a problem may occur. The problem may occur if there is a side-by-side installation of Microsoft Message Queuing, also known as MSMQ, and Message Queuing Transport. The message may not be sent successfully. This problem occurs in Microsoft BizTalk Server 2004.

Back to the top

This problem occurs when Message Queuing does not correctly bind the outgoing TCP/IP socket in Microsoft Windows Server 2003.

Back to the top

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

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
   --------------------------------------------------------------
   26-Jul-2004  21:46  5.2.1727.194      146,432  Mqad.dll         
   26-Jul-2004  21:46  5.2.1727.194      192,000  Mqads.dll        
   26-Jul-2004  21:46  5.2.1727.194        9,728  Mqcertui.dll     
   26-Jul-2004  21:46  5.2.1727.194       31,232  Mqdbodbc.dll     
   26-Jul-2004  21:46  5.2.1727.194       47,616  Mqdscli.dll      
   26-Jul-2004  21:46  5.2.1727.194       48,128  Mqdssrv.dll      
   26-Jul-2004  21:46  5.2.1727.194       44,544  Mqgentr.dll      
   26-Jul-2004  21:46  5.2.1727.194       28,160  Mqise.dll        
   26-Jul-2004  21:46  2001.12.4720.19    71,680  Mqlogmgr.dll     
   26-Jul-2004  21:46  5.2.1727.194      777,216  Mqqm.dll         
   26-Jul-2004  21:46  5.2.1727.194      169,472  Mqrt.dll         
   26-Jul-2004  21:46  5.2.1727.194      117,248  Mqrtdep.dll      
   26-Jul-2004  21:46  5.2.1727.194      133,632  Mqsec.dll        

Back to the top

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

Back to the top

When you configure a side-by-side installation of Message Queuing and Message Queuing Transport, you specify the Message Queuing TCP/IP address in the following registry entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters\BindInterfaceIP

Back to the top

For additional information about a side-by-side installation of Message Queuing and BizTalk Message Queuing, visit the following Microsoft Developer Network (MSDN) Web site: For additional information about standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top