Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

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.

↑ Back to the top


Resolution

Cumulative update information

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

↑ Back to the top


Status

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

↑ Back to the top


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 .

↑ Back to the top


Keywords: kbqfe, kbsurveynew, kbbtsbam, kbexpertiseadvanced, kbfix, kb

↑ Back to the top

Article Info
Article ID : 3058787
Revision : 1
Created on : 1/7/2017
Published on : 10/10/2015
Exists online : False
Views : 419