Microsoft KB Archive/924715

= FIX: Message data is not deleted from the tracking database after you run the bts_CleanupMsgbox stored procedure in a BizTalk Server 2006 test environment =

Article ID: 924715

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2006 Standard Edition
 * Microsoft BizTalk Server 2006 Enterprise Edition
 * Microsoft BizTalk Server 2006 Developer Edition

-



SYMPTOMS
Consider the following scenario. You install Microsoft BizTalk Server 2006 in a test environment. You run the Msgbox_cleanup_logic.sql stored procedure to configure the bts_CleanupMsgbox stored procedure. You run the bts_CleanupMsgbox stored procedure against a message box database.

In this scenario, suspended messages are removed from the message box database as expected. However, the data that is associated with the messages is not deleted from the tracking database.

Note Do not run the bts_CleanupMsgbox stored procedure on a production server that is running BizTalk Server 2006. You should only run the bts_CleanupMsgbox stored procedure in a test environment. Running the bts_CleanupMsgbox stored procedure in a production environment is not supported.



Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

Prerequisites
No prerequisites are required.

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 also 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
By default, the bts_CleanupMsgbox stored procedure exists in each message box database. However, the script for the bts_CleanupMsgbox stored procedure is empty.

When you install BizTalk Server 2006, a schema that is named Msgbox_cleanup_logic.sql is installed in the \Microsoft BizTalk Server 2006\Schema folder. The Msgbox_cleanup_logic.sql file contains the definition for the bts_CleanupMsgbox stored procedure. When you run the Msgbox_cleanup_logic.sql file, the SQL statements that are required to delete suspended messages from the message box database are inserted into the bts_CleanupMsgbox stored procedure.

To update and then run the bts_CleanupMsgbox stored procedure, follow these steps:
 * 1) Contact Microsoft Product Support Services to obtain an updated Msgbox_cleanup_logic.sql schema.
 * 2) In SQL Query Analyzer, run the Msgbox_cleanup_logic.sql file that you obtained in step 1 against each message box database.
 * 3) Stop all BizTalk host instances in the test environment.
 * 4) If you are using the HTTP or SOAP adapter, run the IISRESET command at a command prompt.
 * 5) Stop any custom adapters that are running in out-of-process host instances.
 * 6) In SQL Query Analyzer, connect to each message box database, and then run the exec bts_CleanupMsgbox command.
 * 7) Restart all BizTalk host instances and out-of-process host instances.

