FIX: A SQL Server transaction log may unexpectedly grow very large after you install BizTalk Server 2004 Service Pack 1

After you install Microsoft BizTalk Server Service Pack 1 (SP1), a Microsoft SQL Server transaction log may unexpectedly grow very large. This problem can occur when BizTalk Server is not processing new messages.

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: 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.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.

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.

Prerequisites

You must have BizTalk Server 2004 SP1 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.Note Because of file dependencies, the most recent hotfix that contains these files may contain additional files.

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

This problem occurs when the orchestration engine processes a message, and a correlating subscription is invalid. For example, this problem can occur if BizTalk Server has marked the subscription as deleted, but SQL Server has not yet committed the transaction that will delete the subscription to the MessageBoxDb database. In a trace file, you may receive an internal error message that resembles the following:Although the error occurs in the orchestration, the orchestration does not generate the error message. Because the orchestration does not generate the error message, the BizTalk messaging engine sends the message again.

When the BizTalk messaging engine repeatedly delivers the message to a long-running orchestration, the orchestration repeatedly rehydrates, fails with the "BTXService::DeliverMessageImpl delivered to non-existing subscription!" error, and then dehydrates. This behavior causes high SQL Server activity during the transaction. Therefore, the SQL Server transaction log grows very large.

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