Transaction Timeouts Error while applying the CU patch on BizTalk Server

I recently came across this error when a customer was trying to apply the CU6 patch on their BizTalk environment.

The transaction associated with the current connection has completed but has not been disposed. The transaction must be disposed before the connection can be used to execute SQL statements.


The issue seems to be here was the transaction were getting aborted after about 10 minutes even though the System.Transactions has a timeout set to 200 minutes

Also BAMPrimaryImport database was quite large around 80 GB.




  • We asked customer to clear the data and bring down the size of BAMPrimaryImport.


After doing the above 2 steps CU6 installed successfully.

Related Links


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s