FIX: BizTalk uses unique GUIDs as Application Name in some SQL connections

S’applique à : BizTalk Server 2013 R2 BranchBizTalk Server 2013 R2 DeveloperBizTalk Server 2013 R2 Enterprise


Assume that you use a Data Security application, such as IBM InfoSphere Guardium, that performs the following tasks:
  • Monitors all database connections in the network
  • Stores relevant information
  • Creates reports about the stored information for BizTalk Server applications
In this situation, the Data Security application consistently determines that every connection signifies a new application. Eventually, the volume of stored information becomes overwhelming and causes the program to crash.

Note The Data Security application stores the information per application based on the "Application Name" value that is specified in the connection string.


This problem occurs because BizTalk Server uses a unique GUID for "Application Name" in every connection for certain calls so that the number of recorded "Application Name" elements grows infinitely and triggers conflicts with the monitoring application.


Cumulative update information

This issue was first fixed in the following cumulative updates for BizTalk Server:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


For information about the service packs and cumulative update list for BizTalk Server, see KB 2555976: Service pack and cumulative update list for BizTalk Server .

For more information about BizTalk Server hotfixes, see KB 2003907: Information about BizTalk hotfixes and cumulative update support .