You have a computer that is running Microsoft BizTalk Server 2006 R2 or Microsoft BizTalk Server 2009.
You create a receive location that uses a Windows Communication Foundation (WCF) LOB Adapter SDK-based adapter to receive messages. For example, you use a custom adapter or an adapter from BizTalk Adapter Pack 2.0.
In this scenario, you may experience the following symptoms:
Orchestration instances go into the Dehydrated state.
The receive location does not process new messages.
Additionally, if you monitor the Process\ThreadCount$BTSNTSvc counter in Performance Monitor, you may see the thread count value increase quickly.
If you use the WCF-SQL Server adapter in this scenario, you may also experience the following symptoms:
Exclusive locks appear in database tables, and you find errors in the DTC trace.
You may see the DTCXact transaction open when the program executes DBCC OPENTRAN.
Sys.dm_tran_active_transactions dynamic management view in SQL Server Management Studio returns transaction_type =4 records. The Transaction_type =4 indicates it is a distributed transaction and the commit process has been initiated. However, the distributed transaction is still active and further processing does not take place.
This problem occurs because the time-out value of WCF does not synchronize with the receive time-out when there is no data to poll. Additionally, WCF opens a new channel and waits for messages on the new channel. This may cause a memory leak situation.
To resolve this problem, apply this hotfix.
Cumulative update information
The hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Adapter Pack 2.0.
For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2444952 Cumulative update package 1 for BizTalk Adapter Pack 2.0
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. 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 website:
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.
You must have the WCF LOB Adapter SDK Service Pack 2 (SP2) installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
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.
WCF LOB Adapter SDK SP2 (x86-based)
WCF LOB Adapter SDK SP2 (x64-based)
For more information about working with BizTalk Adapter for SQL Server Binding Properties, visit the following Microsoft website: