Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: You experience performance issues with BizTalk Server 2006 and throttling messages are logged in the performance log file


View products that this article applies to.

Symptoms

You frequently experience performance issues when you use BizTalk Server 2006. For example, you receive Single Sign-On (SSO) time-out error messages. Additionally, the BizTalk Server 2006 Administration console stops responding. If you use the following SQL statement to determine the size of the <BizTalkHostName>Q_Suspended table, you find that the table contains many rows:
Select count (*) from <BizTalkHostName>Q_Suspended
Note <BizTalkHostName> is a placeholder for a customer host name.

Additionally, some throttling messages for the database size are logged in the performance log file.

↑ Back to the top


Cause

This issue occurs because zombie messages are created for the cache service instance. The bts_UpdateMsgbox_BizTalkHostName stored procedure calls the Insert statement to move these zombie messages into the suspended queue. Then, the slow execution time of the stored procedure blocks many other BizTalk Server-related SQL scripts.

Based on the BizTalk Server 2006 mechanism, the large suspended messages for the cache service instances in the database create a throttling problem. This problem occurs when the peak workload value is larger than the default throttling value for the database size.

Note By design, users cannot retrieve or terminate these suspended messages in the BizTalk MMC.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next BizTalk Server 2006 that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

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

Restart requirement

You must restart the following components after you apply this hotfix:
  • All related SQL Server jobs in BizTalk Server 2006.
  • All BizTalk host instances in BizTalk Server 2006.
  • The Internet Information Services (IIS) service.

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.
File nameFile versionFile sizeDateTimePlatform
2453.sqlNot applicable23208-May-200713:37Not applicable
Biztalkcustomactiondata.xmlNot applicable79008-May-200713:47Not applicable
Msgbox_application_logic.sqlNot applicable505,56208-May-200721:39Not applicable
Msgboxschema.sqlNot applicable97,63808-May-200721:39Not applicable
After you install the hotfix, the 2453.sql script and the Msgbox_application_logic.sql script delete the zombie messages for the cache service instances.

↑ Back to the top


Status

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

↑ Back to the top


Keywords: KB936536, kbqfe, kbhotfixserver, kbexpertiseinter, kbbiztalk2006presp1fix, kbbtsmessaging

↑ Back to the top

Article Info
Article ID : 936536
Revision : 3
Created on : 12/10/2010
Published on : 12/10/2010
Exists online : False
Views : 331