Microsoft KB Archive Search

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.

  1. Home
  2. FIX: The Tracking Profile Editor uses the wrong schema when the tracking profile is deployed

FIX: The Tracking Profile Editor uses the wrong schema when the tracking profile is deployed

View products that this article applies to.

Symptoms

Consider the following scenario:

  • You have two versions of a schema that have the same name but are in different assemblies and have different target namespaces.
  • You use the Tracking Profile Editor to deploy a tracking profile by using one of these schemas.
In this scenario, the Tracking Profile Editor uses the wrong schema when the tracking profile is deployed.

↑ Back to the top

Cause

This problem occurs because the Tracking Profile Editor evaluates only the schema name and not the assembly name. In this situation, the deployed tracking profile uses the first instance of the schema name that it finds.

↑ Back to the top

Resolution

Cumulative update information

The fix that resolves this problem is included 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

Keywords: kb, kbqfe, kbsurveynew, kbnotautohotfix, kbfix, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 3123164
Revision : 1
Created on : 1/7/2017
Published on : 4/13/2016
Exists online : False
Views : 365