This site uses cookies and by using the site you are consenting to this. We utilize cookies to optimize our brand’s web presence and website experience. To learn more about cookies, click here to read our privacy statement.

Modernize Integration with BizTalk Upgrade

BizTalk Integration tools help organizations to excavate their data in a structured, reliable and auditable way — and makes data the highest quality. BizTalk Server connects to many disparate internal and external components to enterprise systems so information can flow smoothly and securely in multiple directions.Integration enables the right data to be delivered at right time.

Integration Roadmap

Microsoft has already given clear direction for cloud-hybrid integration roadmap, which BizTalk server is a key part in.

BizTalk Server 2019 “vNext”will be available latter part of this year with availability of Windows Server 2019. BizTalk Server “vNext” will include all previously released feature packs; platform support for the newest versions of Windows Server, SQL Server and Visual Studio; and an upgrade path from BizTalk Server 2013 R2 and BizTalk Server 2016. Microsoft mentioned that new versions of BizTalk are also accompanied by a “vNext” of the Adapter Pack and Host Integration Server.

BizTalk Server and Logic Apps are both capable of running on-premises and in Azure. Microsoft focused on functional gaps in this area to help\ customers planning to migrate from BizTalk Server (On-Prem) to Logic Apps (Azure) and also expanding the capabilities of iPaaS offering, providing additional hosting options for Azure Integration Services. This includes Logic Apps, starting with the ability to run on-premises.

Microsoft Azure Integration Services’ vision is to enable all customers to move to a modern, holistic and rich iPaaS platform that can meet the challenges of all their integration workloads.

BIZTALK 2016 – Why Upgrade Now

New versions contain important changes to improve the performance, stability and security of the applications that run on operating software. Upgrading environment ensures that your software continues to run safely and efficiently.

If your environment is on prior version of BizTalk 2016 then it is already time for upgrading your environment as mainstream support for BizTalk Server 2013 and 2013 R2 versions were ended on 7/10/2018 and currently are under extended support.

Some key features from BizTalk 2016:

  • BizTalk Server 2016 adds support for Microsoft platforms Visual Studio 2015, Windows Server 2016, SQL Server 2016, Office 2016.
  • BizTalk Server Azure VMs in production – BizTalk Server 2016 fully supports Azure virtual machines for production environments. Using SQL Server 2016 AlwaysOn, a highly available solution is now possible.
  • Logic app adapter – Connect to your Logic Apps hosted in Azure, and get access to all the connectors including Salesforce, SharePoint, CRM Online, and more. For example, you can receive an order in BizTalk Server, connect to your Logic App, and update Salesforce.
  • Feature Packs Includes

Office 365 adapters to work with Email, Calendar and Contacts.

Closer integration with API Management, an Azure Event Hubs adapter, backup to Azure blob storage account, support for Service Bus partitions

Includes support for automatic deployment using VSTS, send tracking data to Azure Application Insights and Power BI, advanced scheduling options on receive locations, and more.

  • SFTP adapter is re-engineered to use WinSCP to connect to SFTP; which allows support for more SFTP servers. Client-side logging and additional encryption ciphers are also new.
  • Ordered delivery on dynamic ports – Applies to the adapters that support ordered delivery on static send ports. You can enable the ordered delivery option in the BizTalk Administration console.
  • Import/export parties – The import and export option is separated from the Application. For example, you can export a party without exporting the application. You can import a party without importing the application

Plan for Upgrade

Upgrading Integration environment requires thorough planning and preparation. Even the most basic single-server deployment relies on many variables, and most real-world deployment scenarios extend much further to include multiple servers and eventually clusters of both physical and virtual machines.

Some key things to note before you plan for upgrade:

  • Notify stakeholders ahead of time, including those from various enterprise systems (Ex: Azure, Salesforce, EDI,SAP, Oracle, CRM, DB2, PeopleSoft, etc)
  • Understand new BizTalk tools support and version compatibility with current enterprise systems
  • Gather information on the needs of enterprise and discuss the scope of deployment with the IT professionals, system administrators
  • Discuss with developers who will use BizTalk Server to analyze the specific needs of enterprise and to create deployment roadmap
  • Discuss with external customers and third party developers (as needed)
  • Schedule testing sessions with internal business teams and external customers (ex: B2B with AS2)

Experiencing the Upgrade

There are a few known errors you may come across during BizTalk 2016 upgrade with Windows 2016.

  • Microsoft.NET Framework 3.5 installation error when adding roles and features

This problem occurs when you try to install the Microsoft .NET Framework 3.5 on a server running Windows 10, Windows Server 2016 or Windows Server 2012.


Follow the below steps to fix these errors:

  1. Enable the .NET Framework 3.5 feature using DISM.
  2. NOTE: You need to have installation media or an ISO image for your Windows version to perform this method.
  3. Copy Windows installation media on to server, or mount the Windows ISO image in your system.
  4. Right-click “Command Prompt” and select “Run as administrator“.
  5. Enter command “Dism /online /enable-feature /featurename:NetFx3 /All /Source:<DRIVE>:\sources\sxs /LimitAccess” and press Enter on your keyboard. (Note: you need to replace the <DRIVE> here with the drive letter for the installation media drive or the ISO drive.)
  6. Try installing .NET Framework 3.5 and this error will disappears.
  • Use XslTransform instead of XslCompileTransform

The issue is that all maps Use XSL Transform property defaults are set to to Undefined, and the run-time did not cope with this default. The only fix was to change it to either True or False and re-deploy the maps.

For more information check this link – https://social.technet.microsoft.com/wiki/contents/articles/33537.biztalk-2013-r2-cu2-use-xsl-transform.aspx

  • Issue with PublishCommandPackage in Visual Studio 2015 after installing BizTalk 2016 Feature Update 2 with CU4

The PublishCommandPackage does not load correctly in VS2015 because of the missing signature of the assembly BizTalkApplication.dll 3.13.324.2.

Unzip BizTalkApplication.vsix from C:\Program Files (x86)\Microsoft BizTalk Server 2016\Developer Tools and extract the BizTalkApplication.pkgdef and BizTalkApplication.dll files

Sign assembly – add new signature to the BizTalkApplication.dll assembly and Edit BizTalkApplication.pkgdef with new publickeyToken

Update BizTalkApplication.vsix with new BizTalkApplication.pkgdef and BizTalkApplication.dll files

Uninstall BizTalk application extension from VS2015.

Double click on updated BizTalkApplication.vsix in VS2015 to reinstall with fix.

  • SSO Admin Console tool doesn’t open after BizTalk 2016 install and configurations

Open the Registry Editor.


Add the following string: InstallPath and value: C:\Program Files\Common Files\Enterprise Single Sign-On

  • TDDS failed to read from source database – The SELECT permission was denied on the object.

This issue may occur after installing BizTalk 2016 feature pack 3. To resolve, add BizTalk application users group to the role BAM_EVENT_READER  on BizTalkMsgboxDB .

I will add more information on cloud-hybrid integration in an upcoming post. If any questions (or) looking for help in upgrading your environment send us request here: spr.com/contact us.