FIX: Routing failure reports are not removed from the <BizTalkHostName>Q_Suspended table on a BizTalk Server 2006 server

Consider the following scenario:

• On a Microsoft BizTalk Server 2006 server, you are running a BizTalk application.
• A subscription error occurs, and then you terminate the suspended service instance.

In this scenario, you may notice that the routing failure reports accumulate in the BizTalkHostNameQ_Suspended table. This causes the BizTalkMsgboxDb database to grow.

Note The BizTalkHostName placeholder is a placeholder for the host name.

This problem occurs because the routing failure reports are not removed from the BizTalkHostNameQ_Suspended table. These routing failure reports cannot be seen in the BizTalk Administration console because the BizTalk Administration console queries the Instances table. When you terminate the suspended service instance after a subscription error occurs, the routing failure reports are removed from the Instances table. Also, you cannot terminate the routing failure reports because they are not associated with a service instance.

Hotfix information

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. For more information, see the Readme.txt file that is included in the hotfix package.

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.

Known issue

Some BizTalk databases may not be updated if you change the BizTalk Server group name before you apply this hotfix package. To avoid this issue, rename the BizTalk Server group back to the following default name before you apply the hotfix:

Prerequisites

You must have BizTalk Server 2006 installed to apply this hotfix.

Restart requirement

This hotfix is updating the BizTalkMsgBoxDB database. To avoid errors and unexpected shutdowns during hotfix installation, shut down the SQL Agent service that is running the BizTalk SQL Agent jobs, the IIS service (isolated hosts), and all BizTalk host instances that are running in this BizTalk group. After the hotfix is installed, restart the SQL Agent service, the IIS service, and the BizTalk host instances.

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.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.