Microsoft KB Archive/941690

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

Article ID: 941690

Article Last Modified on 10/19/2007

-

APPLIES TO


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

-



SYMPTOMS
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 Q_Suspended table. This causes the BizTalkMsgboxDb database to grow.

Note The  placeholder is a placeholder for the host name.



CAUSE
This problem occurs because the routing failure reports are not removed from the Q_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 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
You must have BizTalk Server 2006 installed to apply this hotfix.

Restart requirement
You do not have to restart the BizTalk services 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.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Keywords: kbexpertiseinter kbhotfixserver kbqfe KB941690

-

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

© Microsoft Corporation. All rights reserved.