Microsoft KB Archive/924007

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

Article ID: 924007

Article Last Modified on 11/21/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2004 Service Pack 1

-



SYMPTOMS
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 now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next BizTalk Server 2004 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
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:

BTXService::DeliverMessageImpl delivered to non-existing subscription!

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 &quot;BTXService::DeliverMessageImpl delivered to non-existing subscription!&quot; 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:

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

Keywords: kbbtsservpack kbbug kbfix kbpubtypekc kbhotfixserver kbqfe kbbts KB924007

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.