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

File name	File version	File size	Date	Time
Btsadminmsg.dll	3.0.7051.0	112,640	14-Aug-2006	16:23
Btsdbaccessor.dll	3.0.7051.0	71,680	14-Aug-2006	16:21
Btsmessageagent.dll	3.0.7051.0	593,408	14-Aug-2006	16:21
Btsmsg.dll	3.0.7051.0	144,384	14-Aug-2006	16:21
Btsmsgcore.dll	3.0.7051.0	1,042,944	14-Aug-2006	16:21
Btswmiprovider.dll	3.0.7051.0	499,200	14-Aug-2006	16:24
Microsoft.biztalk.interop.agent.dll	3.0.7051.0	45,056	14-Aug-2006	15:42
Microsoft.biztalk.messageboxom.dll	3.0.7051.0	77,824	14-Aug-2006	15:42
Microsoft.biztalk.messaging.dll	3.0.7051.0	53,248	14-Aug-2006	15:51
Microsoft.biztalk.streaming.dll	3.0.7051.0	45,056	14-Aug-2006	15:41
Microsoft.xlangs.basetypes.dll	3.0.7051.0	61,440	14-Aug-2006	15:41
Microsoft.xlangs.biztalk.engine.dll	3.0.7051.0	233,472	14-Aug-2006	15:55
Microsoft.xlangs.engine.dll	3.0.7051.0	229,376	14-Aug-2006	15:55
Microsoft.xlangs.runtimetypes.dll	3.0.7051.0	114,688	14-Aug-2006	15:42
Msgboxlogic.sql	Not Applicable	360,058	14-Aug-2006	15:51
Msgboxschema.sql	Not Applicable	72,374	14-Aug-2006	15:51
Msgbox_application_logic.sql	Not Applicable	398,860	14-Aug-2006	15:51
Msgbox_tracking_logic.sql	Not Applicable	6,618	14-Aug-2006	15:51

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.