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.

RESOLUTION

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

• Modify machine.config file to set the max Timeout to 1 hour.

After doing the above 2 steps CU6 installed successfully.

Related Links

http://msdn.microsoft.com/en-us/library/ee377024(v=bts.70).aspx

http://blog.sabratech.co.uk/2010/08/lessons-learnt-story-of-recent.html

http://richardhallgren.com/bam-tracking-data-not-moved-to-bam-archive-database/

http://blogs.biztalk360.com/biztalk-environment-maintenance-from-a-dba-perspective/

https://social.msdn.microsoft.com/Forums/en-US/12ba5285-9eb1-45f8-abf1-a2afe42b64f6/biztalk-database-too-large-especially-bamprimaryimport?forum=biztalkgeneral