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: It takes a long time to open a BizTalk map in Microsoft Visual Studio 2005 if the schemas of the map are referenced from another BizTalk project in BizTalk Server 2006 R2 or in BizTalk Server 2009

FIX: It takes a long time to open a BizTalk map in Microsoft Visual Studio 2005 if the schemas of the map are referenced from another BizTalk project in BizTalk Server 2006 R2 or in BizTalk Server 2009

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You open a BizTalk project by using Microsoft Visual Studio 2005 on a computer that is running Microsoft BizTalk Server 2006 R2 or Microsoft BizTalk Server 2009.  
  • The BizTalk project contains a BizTalk map. The source schema and the destination schema of the map come from a separate project.
  • The separate project that contains the schemas is added as a project type reference in the BizTalk project that contains the BizTalk map. Or, the development build assembly of the schema project is added as a reference in the map project.
  • You try to open the map in Microsoft Visual Studio 2005.
In this scenario, the map takes a long time to open. Additionally, Visual Studio 2005 may become less responsive while it opens the map.

Note The issue does not occur if the schemas and the map are within the same BizTalk project. If you use BizTalk Server 2009, the Event Source and Event Category in above events are “BizTalk Server 2009”.

↑ Back to the top

Cause

The issue occurs because of an error in the Microsoft.BizTalk.ArtifactBrowser.dll file.

↑ Back to the top

Resolution

Cumulative update information

BizTalk Server 2009

The hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2009.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2497794 Cumulative update package 2 for BizTalk Server 2009

The hotfix that resolves this problem is included in cumulative update package 3 for BizTalk Server 2006 R2 SP1.



For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2286501 Cumulative update package 3 for BizTalk Server 2006 R2 Service Pack 1


For more information about BizTalk Server 2006 R2 SP1 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
974563 List of Microsoft BizTalk Server hot fixes that are included in BizTalk Server 2006 R2 Service Pack 1

For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

2003907 Information on BizTalk Server hotfixes

↑ Back to the top

Workaround

To work around this issue, add a reference to the deployment build assembly of the schema project in the map project.

↑ 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

More Information

For more information about how to test a map, visit the following Microsoft Developer Network (MSDN) website:
Testing a map

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2285536
Revision : 1
Created on : 1/7/2017
Published on : 3/18/2011
Exists online : False
Views : 391