Microsoft KB Archive/940519

= Known issues in BizTalk Server 2004 Service Pack 2 that are not documented in the ReadmeSP2.htm file =

Article ID: 940519

Article Last Modified on 7/25/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2004 Service Pack 2

-



INTRODUCTION
This article describes the known issues in Microsoft BizTalk Server 2004 Service Pack 2 (SP2) that are not documented in the ReadmeSP2.htm file.



Issue 1: The BizTalk Server 2004 SP2 installation appears to stop responding when you clear the BizTalk Tracking database
When you install BizTalk Server 2004 SP2, a dialog box displays the number of rows that will be processed when you clear the BizTalk Tracking database (BizTalkDTADb). After you click Continue, the status of the installation is not updated until the BizTalk Tracking database is completely cleared. The clearing process may take several hours if one or more of the following conditions are true:
 * The BizTalk Tracking database is very large.
 * Multiple instances of BizTalk Server 2004 are running an instance of an adapter handler under an isolated host.

To reduce the time that is required to clear the tracking data from the BizTalk Tracking database, use the following method that is appropriate.

Method 1: Reduce the size of the BizTalk Tracking database before you install BizTalk Server 2004 SP2
If the BizTalk Tracking database is very large, consider running the dtasp_PruneTrackingdatabase stored procedure before you install BizTalk Server 2004 SP2. For more information about the pre-BizTalk Server 2004 SP2 version of the dtasp_PruneTrackingdatabase stored procedure, click the following article number to view the article in the Microsoft Knowledge Base:

894253 FIX: The dtasp_PruneTrackingdatabase stored procedure may take many hours to clean up the DTA database in BizTalk Server 2004

Method 2: Stop all the instances of adapter handlers that are running under isolated hosts
To reduce the time that is required to clear the tracking data from the BizTalk Tracking database, stop all the instances of adapter handlers that are running under isolated hosts in the BizTalk Server 2004 environment. For example, stop the following instances:
 * All the instances of HTTP receive handlers and of SOAP receive handlers
 * Instances of adapter handlers that run under isolated hosts in Internet Information Services (IIS) 6.0 application pools
 * Instances of adapter handlers that run under isolated hosts in a Microsoft COM+ application on a server that is running BizTalk Server 2004 and IIS 5.0

Issue 2: The BizTalk Server 2004 databases and the SQL Server Agent jobs are not restored when you uninstall BizTalk Server 2004 SP2
When you uninstall BizTalk Server 2004 SP2, the BizTalk Server 2004 SP2 binaries are removed. Additionally, the Microsoft BizTalk Server 2004 Service Pack 1 (SP1) binaries are restored as expected. However, BizTalk Server 2004 SP2 includes significant database schema changes. When you uninstall BizTalk Server 2004 SP2, the BizTalk Server 2004 databases are not restored to the BizTalk Server 2004 SP1 state. Additionally, when you uninstall BizTalk Server 2004 SP2, the SQL Server Agent jobs are not restored to the state that existed before you installed BizTalk Server 2004 SP2.

To make sure that BizTalk Server 2004 works as expected when you uninstall BizTalk Server 2004 SP2, follow these steps:
 * 1) Before you install BizTalk Server 2004 SP2, verify that you have a backup of the BizTalk Server 2004 databases. When you uninstall BizTalk Server 2004 SP2, restore the BizTalk Server 2004 databases from the existing backup.
 * 2) Before you install BizTalk Server 2004 SP2, generate SQL scripts for the SQL Server Agent jobs. When you uninstall BizTalk Server 2004 SP2, re-create the SQL Server Agent jobs from these SQL scripts. For more information about how to generate SQL scripts for the SQL Server Agent jobs, see the Microsoft SQL Server Help documentation.

Keywords: kbbtsservpack kbbts kbtshoot kbreadme kbinfo KB940519

-

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

© Microsoft Corporation. All rights reserved.