This article has been archived. It is offered "as is" and will no longer be updated.
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.
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.
No prerequisites are required.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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:
Contact Microsoft Product Support Services to obtain an updated Msgbox_cleanup_logic.sql schema.
In SQL Query Analyzer, run the Msgbox_cleanup_logic.sql file that you obtained in step 1 against each message box database.
Stop all BizTalk host instances in the test environment.
If you are using the HTTP or SOAP adapter, run the IISRESET command at a command prompt.
Stop any custom adapters that are running in out-of-process host instances.
In SQL Query Analyzer, connect to each message box database, and then run the exec bts_CleanupMsgbox command.
Restart all BizTalk host instances and out-of-process host instances.
For more information, 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