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.

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.

Resolution

Cumulative update information

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

Learn about service pack and cumulative update list for BizTalk Server.

Learn about BizTalk Server hotfixes and cumulative update support.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×