BizTalk Server 2010 – List of Known Issues and Solutions (Part 1)

The following are the known issues in BizTalk Server 2010:

Known Issues with Orchestration

Issue: When redeploying an existing Orchestration solution, you do not receive a warning message when referring to an older assembly from GAC; also, there is no way to figure out if you are getting an old assembly instead of a new assembly.


  • Before doing redeployment from Visual Studio, terminate BizTalk management console (mmc.exe), and then make sure you have checked the RestartHostInstance checkbox in BizTalk Server project deployment tab.

Issue: When Add Web reference in Design Tools does not show port type in BizTalk Orchestration Designer. The unexpected behavior in BizTalk Design tools is due to a known limitation of Visual Studio 2010.


  • You need to install QFE patch for Visual Studio 2010 to fix this issue.

Known Issues with Mapper Activity

You might encounter the following error message when building a workflow project with mapper activity:

Issue: The referenced assembly “Microsoft.ServiceModel.Channels.MapperActivity” could not be resolved because it has a dependency on “System.Web, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” which is not in the currently targeted framework “.NETFramework,Version=v4.0,Profile=Client”.


  • Change/retarget the project to .NET Framework 4. For more information, see How to: Target a Specific .NET Framework Version or Profile

Issue: Maps defined in a referenced assembly or a referenced project cannot be edited or opened from the associated Mapper activity.


  • Open the project containing the map and edit the map. You are required to rebuild the project once you update the map.

Known Issues with WCF LOB Adapter SDK

You might encounter the following issues when working with the BizTalk Adapter Pack:

Issue: An error for an unrecognized element is shown when you try to open the AppFabric Endpoint Management tool or IIS Config Editor in IIS Manager for a service that uses BizTalk Adapter Pack.


Issue: On a 64-bit computer on which both 64-bit and 32-bit versions of BizTalk Adapter Pack is installed, the uninstallation of one will lead to configuration properties not showing up on IIS Config Editor.


  • Run the setup again and repair the installation.

Known Issues with Developer Tools

Issue: Known issue with import of older binding files with EDI party migration.

Importing older binding files for BizTalk Server applications that include EDI party data is not blocked. We recommend that you do not import bindings to migrate EDI party data from BizTalk Server 2006 R2 or BizTalk Server 2009 to BizTalk Server 2010.

TIP: Use the party migration tool for all EDI party migrations.

Issue: On adding an existing BizTalk Pipeline file to a BizTalk project, the build can fail due to some errors in the BizTalk Pipeline file.


  • Add all the desired assemblies from %BTSINSTALLPATH%Pipeline components to the project references.
  • If the BizTalk project has Custom Component(s), then you need to add all the relevant assemblies and projects to the project references. For more information on Developing Custom Pipeline Component.

Known Issues with UDDI

Users cannot access the UDDI portal if the ‘Application Pools’ setting points to .NET Framework 4


Ensure that the Application Pool Default settings points to.NET Framework 2.0 before configuring UDDI. The steps to change the Application Pool Default Settings in Internet Information Service (IIS) are:

  • Open IIS Manager on the computer where UDDI needs to be configured:
    • Click Start > Run.
    • Type inetmgr to open IIS Manager, and then click OK.
  • In the Connections pane of IIS Manager, expand <Computer Name> node, and then click Application Pools.
  • In the Actions pane, click Set application pool defaults.
  • In the General section, ensure that the .NET Framework version is set to 2.0, and then click OK.

Known Issues with TPM

Issue: Users get the following error when viewing agreements and protocol settings through the BizTalk Server Administration console when SSO is not configured on the computer:

Could not contact the SSO server ‘MM2009X86SSO’. Check that SSO is configured and that the SSO service is running on that server.


  • Install and configure SSO on every computer running the BizTalk Server Administration console.

Known Issues with SWIFT Accelerator

Issue: You may see an unexpected event error (Event ID: 1040) during the installation of Microsoft BizTalk Accelerator for SWIFT


  • You need to unconfigure and then reconfigure Microsoft Biztalk Accelerator for SWIFT.

Issue: Microsoft BizTalk Accelerator for SWIFT 2010 Message Pack configuration does not start automatically after the installation and configuration of Microsoft BizTalk Accelerator for SWIFT

As part of BizTalk Accelerator for SWIFT installation, BizTalk Accelerator for SWIFT 2010 Message Pack gets installed as a pre-requisite. After BizTalk Accelerator for SWIFT installation, its Configuration User interface is launched automatically, but there is no intimation given to the users to configure BizTalk Accelerator for SWIFT 2010 Message Pack. As a result, warning messages may be reported in the event log and message processes may fail.


  • You need to manually configure Microsoft BizTalk Accelerator for SWIFT 2010 Message pack after installing and configuring Microsoft BizTalk Accelerator for SWIFT. It should be done from Start> All Programs> Microsoft BizTalk Accelerator for SWIFT 2010 Message Pack > BizTalk Accelerator for MessagePack Configuration.

Known Issues with Runtime

Issue: BizTalk Server Application Service (BTSNTSvc.exe) fails to start automatically after a system restart.


  • You can use one of the following ways to start the BizTalk Server Application Service:
    • Manually start the BizTalk Service BizTalk Group : BizTalkServerApplication Service from Services.msc.
    • In Services.msc, set the Startup type for Enterprise Single Sign-On Service and BizTalk Service BizTalk Group : BizTalkServerApplication service to Automatic (Delayed Start).

Issue: BizTalk Server Application Service (BTSNTSvc.exe) fails when you try to manually start or stop it. You will see the event error Event ID: 1053.


  • Ensure that the credentials for SQL Server service are correct. You should be able to restart the SQL Server service and BizTalk Server Application Service (BTSNTSvc.exe) successfully.

Known Issues with Migration

Issue: Migration of a project from Visual Studio 2005 to Visual Studio 2010 fails if the project does not have the solution file


  • Ensure that the .sln and .btproj files are present in the BizTalk project during migration.

Issue: BAM migration from BizTalk Server 2009/2006 R2 to BizTalk Server 2010 might fail if there are active handles to the BAMAlerts service


  • Before starting the BAM migration process, ensure that all the active handles (ex: service explorer window) are closed.
Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

3 thoughts on “BizTalk Server 2010 – List of Known Issues and Solutions (Part 1)”

    1. Hi Rajat,

      At the moment I don’t know if these issued exist in BizTalk 2013, you can find a list of known issues in this release of the BizTalk Server 2013 here:

      However If some of the issues of BizTalk Server 2010 involve installing hotfix, this for sure don’t apply in BizTalk Server 2012, other issues that don’t need hotfix and can be solved with some workaround, if they exist in BizTalk Server 2013 provably you can apply the same workaround solution, but like I say previous, at this moment I don’t know.

Leave a Reply

Your email address will not be published. Required fields are marked *


Back to Top