Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: The MSMQT adapter may unexpectedly stop processing messages if you experience database failure or intermittent connectivity issues in BizTalk Server 2004

FIX: The MSMQT adapter may unexpectedly stop processing messages if you experience database failure or intermittent connectivity issues in BizTalk Server 2004

Symptoms

In Microsoft BizTalk Server 2004, the MSMQT adapter may unexpectedly stop processing messages from a Microsoft Message Queuing client. Additionally, the MSMQT adapter may reject subsequent messages from the Message Queuing client. Therefore, messages accumulate in the outgoing queue of the Message Queuing client.

This problem may occur if you experience database failure or intermittent database connectivity when BizTalk Server processes a message.

↑ Back to the top

Resolution

Hotfix information

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:
http://support.microsoft.com/contactus/?ws=support
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

You must have Microsoft BizTalk Server 2004 installed to apply this hotfix.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 item in Control Panel.
File nameFile versionFile sizeDateTimeSP requirement
Msmqt.dll3.0.7040.0308,22405-Jul-200621:06
Msmqtn.dll3.0.7040.0160,76805-Jul-200621:06
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

↑ Back to the top

More Information

When you receive a message, the MSMQT adapter starts a transaction to process the message. The MSMQT adapter sends an acknowledgement message and an order acknowledgement message to the Message Queuing client. If BizTalk Server cannot commit the transaction because connectivity issues occur with the database, the transaction is rolled back. However, because the order acknowledgement has already been sent, the client will increment the sequence number that is used to track transactions. This behavior may cause the MSMQT adapter and the Message Queuing client not to be synchronized.

For example, the Message Queuing client sends a message that has a sequence number of 100. The Message Queuing client increments the sequence number to 101 when it receives the order acknowledgement. Therefore, the next message that the Message Queuing client sends has a sequence number of 101. However, if BizTalk Server cannot commit the transaction that has the sequence number of 100 to the database, BizTalk Server expects the next transaction to have a sequence number of 100. This behavior causes the MSMQT adapter to reject subsequent messages from the Message Queuing client that have a sequence number of 101 or more.

↑ Back to the top

Status

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

↑ Back to the top

More Information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kbqfe, kbhotfixserver, kbpubtypekc, kbfix, kbbts, kbentirenet, kb, kbbiztalk2004sp2fix, kbautohotfix, kbbug

↑ Back to the top

Article Info
Article ID : 918343
Revision : 1
Created on : 3/25/2017
Published on : 9/23/2011
Exists online : False
Views : 658