Biztalk 2010 Cumulative update 6 and BizTalk Adapter Pack cumulative update 3

On July 16th, the new CU (cumulative update) package for BizTalk 2010 became available . This CU contains lot of kb (see the list below)
For BizTalk 2010, you can download here :
BizTalk Server EDI support

KB article number Description
2777584 FIX: The value for the « maxOccurs » attribute is invalid when you validate the BizTalk X12 EDI 835 schema in a BizTalk EDI application in BizTalk Server 2010
2778133 FIX: Message is suspended when you try to receive an encrypted AS2 message together with asynchronous MDN in BizTalk Server 2010
2858166 FIX: « Too many data elements » error when you receive an EDI X12 997 message in BizTalk Server 2010
BizTalk Server Adapters
KB article number Description
2811803 FIX: First submitted message takes longer to process than expected after periods of inactivity when you use a BizTalk Server 2010 WCF-Custom adapter
2855762 FIX: SQL connection leak when you use WCF-based SQL Adapter one-way send port to return a result set from a database in BizTalk Server 2010
2813294 FIX: 2-way WCF-BasicHttp receive port does not respond to a WCF client when the « failed message routing » feature is enabled in BizTalk Server 2010
2823757 FIX: The memory that a BizTalk host process consumes increases when there are no messages in the queue in BizTalk Server 2010
2804250 FIX: You cannot send files from an FTP server to BizTalk Server 2010 by using the FTP adapter when you specify a temporary folder as an absolute path
2742875 FIX: JDE and TibcoEMS adapter property assemblies contain no namespace and all properties are missing in BizTalk Server 2010

BizTalk Server Design Tools

KB article number Description
2818904 FIX: NullReferenceException exception when you use the « BizTalk WCF Service Publishing Wizard » to publish schemas as WCF services
BizTalk Server Message Runtime, Pipelines, and Tracking
KB article number Description
2792865 FIX: A send port that subscribes to an ErrorReport namespace context property cannot deliver an output message in BizTalk Server 2010
2802453 FIX: Pipeline on receive locations reverts to pass-through after you update the schema assembly in BizTalk Server 2010
2836801 FIX: « The transaction has already been implicitly or explicitly » error message when you deploy a large tracking profile in BizTalk Server 2010
2689953 FIX: XML declaration is removed at a receive location that uses BAM tracking and the PassThruReceive pipeline in BizTalk Server 2010

BizTalk Server Administration Tools and Management APIs

KB article number Description
2728652 FIX: The tracking settings of PassThruTransmit and PassThruReceive pipelines are unexpectedly discarded when you remove a BizTalk application in BizTalk Server 2010
2749592 FIX: Slow performance when System Center Operations Manager monitors a computer in BizTalk Server 2010

BizTalk Server Orchestration engine

KB article number Description
2835689 FIX: « The InnerText property is write only » error message when you use System.Xml.XmlDocument in BizTalk Server 2010

For BizTalk Adapter pack, you can download here :

VSTS bug number KB article number description
1249726 2845542 FIX: Package variables trigger operations fail when you use BizTalk Adapter for Oracle Database to connect to Oracle Database
1249588 2845538 FIX: « Column ‘PROVIDERTYPE’ does not belong to table SchemaTable » exception when you use BizTalk Adapter for Oracle Database to connect to an Oracle database
1266767 2845536 FIX: Messages become stuck in SM58 when you use a WCF-based SAP Adapter in BizTalk Server 2010
1243883 2836739 FIX: WCF-SAP adapter receive location freezes under heavy load when it works as a tRFC server
1158982 2800376 FIX: WCF-based SQL Adapter stops polling data when daylight saving time ends
1152657 2795080 FIX: SQL Server connections are not released when invalid messages are passed by the WCF-SQL adapter
1055658 2761439 FIX: Configured time-out value for adapter binding properties does not work when a WCF workflow application uses an adapter to connect an LOB Server instance
1031951 2746855 FIX: Database connection leak when you use Microsoft BizTalk Adapter for Oracle Database to receive messages from an Oracle database in BizTalk Server 2010

BizTalk: List of Errors and Warnings, Causes and Solutions

A client ask me to create a wiki about BizTalk errors and how to clear it.

A quick search on your favorite search engine give me a great technet article.

I share it with you because it covers a lot of errors and the explanations are efficients

Don’t forget to add it in your favorites

Performance issue : a love story with the SQL Agent

Hey everybody,

Just for fun, some relations told me about their biztalks servers issues during load test sessions.

They rans too much slowly and get a lot of dead lock on the messagebox. I start by analyzing job agent state.

And here it is, the SQL agent is not RUNNING  since a long time.

Consequence : the messagebox of course grows up. Immediatly, I enable the agent and start all essential job.

After 2 hours the jobs finished and the database size is nearly acceptable.

But the problem still exist, so I checked the log size and surprise they weight around 150go, the problem continues.

The job keeps the log history for 30days, so my client got two choices :

  • wait one month in this mode
  • purge the SQL log

My client chose the first as I advice him. the reasons why :

  • This procedure is not supported by Microsoft
  • The purge procedure is very dangerous
  • As I said in the beginning, the issues are encountered only in load performance, for the existing flows there is no problems

Now log size is supervised they wait for the log diet

In conclusion, please check the job agent is very crucial.

For those who want what is the procedure to clear all BizTalk logs, here is the script

USE master
Use BizTalkMgmtDb

Use BizTalkDTADb
Use BizTalkMsgBoxDb

USE master

Performance issue in Development plateform : one solution clean your BizTalk DB

My dev machine works so slowly, so I decided to clean it. I found a guide to perform it.

But don’t do it on production plateform, it won’t be supported

Here are few steps to clean up BizTalk Message Box Database.

1. There is a Stored Proc bts_CleanupMsgbox in BizTalkMsgBoxDb Database. By default this stored proc does nothing. It’s Dummy. This is to prevent accidental execution in the Production Server.

2. Execute a script to recreate bts_CleanupMsgbox. Script can be found at <BizTalk Dir>\Schema\msgbox_cleanup_logic.sql. This script should be executed in BizTalkMsgBoxDb Database.

3. Stop BizTalk services from the Services (Start -> Run -> Services.msc).

4. Reset IIS server incase if you have any running isolated host instances

5. Execute stored procedure bts_CleanupMsgbox on your message box database

This SP will take an input parameter @fLeaveActSubs.
Values for this should be ’0′ or ’1′. ’1′ is the default incase if you dont supply a value.

Setting the value to ’0′ results in clearing the active subscriptions and you may have to redeploy the application. Think twice before doing this.

6. The above will not clear off all the subscription but will mark for deletion . Execute the stored procedure bts_PurgeSubscriptions on your message box database to purge them all.

7. Start BizTalk services

To clean up the Tracking data in BizTalkDTADb Database

1. Stop BizTalk services from the Services (Start -> Run -> Services.msc).

2. Execute stored procedure dtasp_CleanHMData on BizTalkDTADb database.

3. Start the BizTalk services

source (

Create BizTalk Adapter using power shell

For production environnement, you potentially don’t have any access to the plateform, so you need to script any object creation. Here is the guid to script adapter creation.

On your development environement you need to get two importants parameters :

  • Create your adapter on your BizTalk adapter -> create new adapter
  • Put a name and a comment
  • Apply
  • Open SQL Management Studio
  • connect the BizTalkLMgmtDb
  • execute this query : SELECT Name, Capabilities, MgmtCLSID  FROM [BizTalkMgmtDb].[dbo].[adm_Adapter] WHERE name=‘YourAdapterName’
  • capabilities is the adapter constraints (clic here to understand how does it work)
  • MgmtCLSID  is the Adapter ID
  • Next in your power shell create this method
  • the parameters$Name, $Comment are the same  that you indicate in the create adapter windows :

function CreateadapterInstance($Name,$Comment)

     $AdapterClass = [wmiclass] « root\MicrosoftBizTalkServer:MSBTS_AdapterSetting »

     $Adapter = $AdapterClass.CreateInstance()
     $Adapter.MgmtCLSID = « {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} »  #Be careful a guid must be provided with brace for WMI 

     $Adapter.Constraints = 1100001011 #convert the capabilities number in binaries format

BTS high availability

Microsoft gives a great articles’ serie about High availability in BizTalk. They provides a lot of advice when installing a very stressed BizTalk environment;

Some concerns SQL, and other windows environement, but all are required; in my experience, I always followed this requirements.


MDSN is a huge online repository for Microsoft documentation. This should be your primary source for information on BizTalk availability:


The following articles provide more information on High Availability for BizTalk:


The following blog posts by community provide more background information and experience on High Availability for BizTalk:


The following web casts by community provide more background information on High Availability for BizTalk:

See Also

source :

SQL-WCF port and OperationName

When you generate a binding with Add generated item ->consume WCF adapter and import it in BizTalk you could meet this issue when you try to test it :

The adapter failed to transmit message going to send port "WcfSendPort_SqlAdapterBinding_TypedProcedures_dbo_Custom" with URL "mssql://.//MeteorLogging?". It will be retransmitted after the retry interval specified for this Send Port. Details:"Microsoft.ServiceModel.Channels.Common.UnsupportedOperationException: The action "<BtsActionMapping xmlns:xsi="" xmlns:xsd="">
  <Operation Name="spBTS_WebUp_Meteor_EntLibLogging_WriteLog" Action="TypedProcedure/dbo/spBTS_WebUp_Meteor_EntLibLogging_WriteLog" />
</BtsActionMapping>" was not understood.

Lire la suite