FIX: BAM tracking does not work as expected for messages that correspond to multi-root schemas in BizTalk Server

Symptoms

Consider the following scenario:
  1. You are using Microsoft BizTalk Server 2013 R2 or Microsoft BizTalk Server 2013.
  2. You have BizTalk application that has a multi-root schema. For example, the schema includes RootNode1, RootNode2, and RootNode3.
  3. You create a BAM tracking profile that includes a track point for tracking data from messages of the RootNode2 type.
In this scenario, BAM records are generated in the bam_ActivityName_x table for messages of all three roots type. You expect that BAM records will be generated only for messages of the RootMode2 type.

Resolution

Cumulative update information

This problem was first fixed in the following cumulative update for BizTalk Server:

Status

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

References

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 .
Propriedades

ID do Artigo: 3058787 - Última Revisão: 10/10/2015 - Revisão: 1

Comentários