Article ID: 905830 - View products that this article applies to.
When the XLANG engine in Microsoft BizTalk Server 2004 is under heavy stress, the XLANG engine may not report a failed Distributed Transaction Coordinator (DTC) transaction. Additionally, the XLANG engine may not end the transaction in BizTalk Server 2004. This problem may occur when the transaction is in an atomic scope.
For example, the XLANG engine may not end the transaction and may not report the failure when a DTC transaction fails because of a time-out. Under these conditions, data may be lost, and system integrity may be compromised.
Hotfix informationA 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:
Warning You cannot roll back this hotfix from the BizTalk Server environment. Therefore, make sure that you fully test this hotfix in a test environment before you apply this hotfix to a production environment. Do not try to use Add or Remove Programs to remove this hotfix because this does not roll back the database changes, and leaves the BizTalk Server environment in an inconsistent state.
PrerequisitesTo apply this hotfix, you must have BizTalk Server 2004 Service Pack 1 (SP1) installed on the computer.
Restart requirementYou must restart the BizTalk Server Application Service after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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.
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Date Time Version Size File name ------------------------------------------------------------------------------ 10-Aug-2005 19:12 3.0.6147.0 592,384 Btsmessageagent.dll 10-Aug-2005 19:12 3.0.6147.0 1,041,408 Btsmsgcore.dll 10-Aug-2005 18:34 3.0.6147.0 45,056 Microsoft.biztalk.interop.agent.dll 10-Aug-2005 18:42 3.0.6147.0 53,248 Microsoft.biztalk.messaging.dll 10-Aug-2005 18:34 3.0.6147.0 45,056 Microsoft.biztalk.streaming.dll 10-Aug-2005 18:46 3.0.6147.0 221,184 Microsoft.xlangs.biztalk.engine.dll 10-Aug-2005 18:46 3.0.6147.0 221,184 Microsoft.xlangs.engine.dll 10-Aug-2005 18:42 300,216 Msgboxlogic.sql
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 905830 - Last Review: October 9, 2011 - Revision: 2.0
Contact us for more help
Connect with Answer Desk for expert help.