In Microsoft BizTalk Server 2006 R2, you import a BizTalk application .msi file by using the BizTalk Administration console. Then, you try to import the same BizTalk application .msi file again. When you do this, the number of connections to Microsoft SQL Server may increase to over 500. The number of connections to SQL Server does not decrease even after the import operation has finished.
Additionally, the import operation may be unsuccessful, and you may receive the following error message:
Import fails with the following: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. (Microsoft.BizTalk.ExplorerOM)
This problem occurs only when you import the same BizTalk application .msi file again. This problem does not occur when you first deploy the BizTalk application .msi file.
Note You can examine the number of connections to SQL Server by running the following query in SQL Server.
Select count(*) from sysprocesses
To correct this behavior, install the hotfix that is documented in Microsoft Knowledge Base (KB) article 954814:
954814 FIX: Importing an .msi file may take a very long time or you may get a "Timeout expired" error
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Microsoft BizTalk Server 2006 R2 Standard Edition, Microsoft BizTalk Server 2006 R2 Enterprise Edition, Microsoft BizTalk Server 2006 R2 Developer Edition, Microsoft BizTalk Server 2006 R2 Branch Edition