BizTalk 2020 – CU4

BizTalk 2020 come out last week, you can find the details here

There are Adapters fixes for 2 x WCF-SAP, WFC-OracleDB, Office365 (Outlook & TMS) & Event Hub.

For the runtime FIX: Excessive CPU usage in kernel mode of Windows when you run multiple BizTalk host instances

A fix for how maps treat whitespaces, this one a fix for where it ignored the default element value if it was only whitespace. FIX: Default element value of spaces or tabs is ignored when using the .NET transform engine in a BizTalk map

A FIX: Turning on auditing causes errors in the BizTalk Server Administration Console

Also of note are the version of components you will need.

Updated External Dependencies

DependencyUpdated version
WinSCP5.19.2
Newtonsoft.Json13.0.1
WindowsAzure.ServiceBus6.2.0
Saxon-HE9.9.1.7
Microsoft.Identity.Client4.36.0
Microsoft.ApplicationInsights2.18.0

If you have BizTalk Developer Tools installed, you must install the latest version of BizTalk Server Visual Studio extension (build 3.13.2.0) in addition to this CU package. The extension can be installed from https://marketplace.visualstudio.com/items?itemName=ms-biztalk.BizTalk or from within Visual Studio through Manage Extensions.

Always check Service Pack and cumulative update list for BizTalk Server for the latest CU for both core BizTalk and Adapters for Enterprise Applications, for HIS check HIS Update Center

Advertisement

BizTalk 2020 CU 3

BizTalk 2020 CU 3 is now available at, KB5007969 – Cumulative Update 3 for Microsoft BizTalk Server 2020

Fixes for adapters include

  • WCF fix for proxy settings
  • 2 fixes for MQSeries
  • 2 fixes for WCF-SAP
  • 1 fix for the SharePoint adapter
  • 1 fix for the Office365 Outlook Email adapter

Improvements

On the blog post that announced it, they also say

As a quick reminder, for BizTalk Developer Tools please also update/install version 3.13.2.0 of the BizTalk Server Visual Studio extension in addition to installing the CU package. The extension can be installed from https://marketplace.visualstudio.com/items?itemName=ms-biztalk.BizTalk or from within Visual Studio – Manage Extensions. Please note that we have not updated the extension since CU1 so you can skip this step if you have already installed it previously.

BizTalk Server 2020 CU2 is available

As per the announcement by Microsoft BizTalk Server 2020 CU2 is available for download.

For the adapters, SFTP gets 4 fixes, the SB-Messaging adapters 3 fixes, the SAP adapter two fixes and one fix each for the WCF-SQL, Logic App adapters.

Also included is a fix to address configuring log shipping, and also a fix that prevented host instances and admin console not starting if the default web proxy is disabled, a fix for a receive location polling outside the service window and an Arithmetic overflow with convoy messages. Import/export of send handler will now include the configured send handler. And a fix for a null reference error when searching in Archived DTA DB.

Also three fixes for development either not surfacing errors or becoming non-responsive. As per the announcement you need to update your extension if you haven’t already done so.

As a quick reminder, for BizTalk Developer Tools please also update/install version 3.13.2.0 of the BizTalk Server Visual Studio extension in addition to installing the CU package. The extension can be installed from https://marketplace.visualstudio.com/items?itemName=ms-biztalk.BizTalk or from within Visual Studio – Manage Extensions. Please note that we have not updated the extension since CU1 so you can skip this step if you have already installed it previously.”

Cumulative Update 8 for Microsoft BizTalk Server 2016

Note: Microsoft have release CU 8 for BizTalk 2016 Feature Pack CU 8 can be found here, you should not install a CU only, if you have a feature pack installed, see BizTalk 2016 Feature Pack vs BizTalk 2016 CUs

This CU contains fixes for following fixes for Adapters

There the two remaining fixes are for BizTalk Server Setup and Configuration “Cannot insert duplicate key row in object ‘dbo.bts_LogShippingHistory’ with unique index” error while configuring log shipping destination

And BizTalk Server Accelerators Digest is not injected in the ACK in FileAct SnF PUSH mode when signature and non-repudiation are requested

BizTalk 2020 CU1 released

BizTalk 2020 CU1 was released on July 28th 2020 as announced here

As per previous version of BizTalk it has a number of SAP/IDOC fixes.

Fixes

  • 4 SAP/IDOX
  • 2 fixes related to the WCF-SQL adapter (order of elements and FILESTREAM operations)
  • 1 for the Oracle DB adapter to handle Database artifacts with nested types in Oracle 18c and later versions
  • Fix for predefined WCF Bindings not taking in account a default Web proxy configuration
  • 2 JSON Encoder fixes (1 one which was fixed for BizTalk 2016 in CU7)
  • Fix for XLTS errors not being reported in XSLT stylesheet
  • Fix for EDI receive location with named SQL instance
  • Fix for ESB Toolkit to use gMSA.
  • Fix to remove dependency on VS 2019 version 16.3.9
  • FIX: Mapper toolbox not working for WCF Workflow Service Application after upgrade to BizTalk 2020

Improvements

  • FTP improvement (macros for Before Put and After Put)
  • Dynamic send ports able to use Officer 365 Outlook adapter types.

Visual Studio Extension

In addition to installing CU package, also update/install new version of BizTalk Server Visual Studio extension (3.13.2.0). The extension can be installed from https://marketplace.visualstudio.com/items?itemName=ms-biztalk.BizTalk or within Visual Studio – Manage Extensions.

As per other CUs, you can find them on the page Service Pack and cumulative update list for BizTalk Server

Cumulative Update 7 for Microsoft BizTalk Server 2016

CU 7 for BizTalk Server 2016 has been released, and also Microsoft BizTalk Server 2016 Feature Update 3 with CU7

Important: Do not mix installing CU’s and Feature packs.

This CU contains

  • Four fixes/improvements for the SFTP adapter.
  • One fix for the IBM MQ.
  • One improvement for the the MQSeries adapters.
  • One fix for SAP (NCo) adapter.
  • One fix for the HL7 BizTalk Server Accelerators.
  • Five fixes around applying CU’s, Feature Packs and other setup and configuration changes (not counting the SFTP one which I’ve counted under adapters).
  • And a JSON FIX: JSON encoder unable to handle XML schema with the same name for record and one of its elements which is an issue that has caused grief for a few people.

Note: It has been reported on Twitter that “We have some issues with the new #biztalk CU7. The json encoder has started formatting boolean values as string values, like “true” instead of true.” and “As we wanted the FTP fixes in CU7 we installed it anyway and replaced the jsonextension dll with an older version.”

In that same thread “Little warning, rolling back CU7, does not rollback the jsonextension version.”

Also JSON encoder pipeline doesn’t create json array after installing CU7

July 2018 Microsoft Security Updates cause BizTalk Admin Console errors: An internal failure occurred for unknown reasons (WinMgmt) #msbts

New Update:   As this issue re-occurred, we applied to fix as per Randy Ridgely in this thread: Microsoft Security Updates cause BizTalk Admin Console errors: An internal failure occurred for unknown reasons (WinMgmt) 

 


Update:
This issue is supposedly resolved in August 2018 .NET Framework Security and Quality Rollup

An update on my earlier blog post An internal failure occurred for unknown reasons (WinMgmt)

Below are the KB numbers for the monthly rollups and security only patches that have impacted or could impact various version of BizTalk Admin Console on different operating systems as per the Technet thread, Sandro’s blog, Stack Overflow and Twitter.

Sandro’s blog also describes the steps for uninstalling.

Monthly Rollup Security Only .Net OS BizTalk
KB4338415 KB4338600  .NET Framework 4.5.2 Windows 8.1, RT 8.1, and Server 2012 R2 BT2010-2013R2
KB4338416 KB4338601 .NET Framework 4.5.2 Windows Server 2012 BT2010-2013R2
KB4338417 KB4338602 .NET Framework 4.5.2 Windows 7 SP1, Server 2008 R2 SP1, and Server 2008 BT2010-2013R2
KB4338815 .NET Framework 4.5.2 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 BT2010-2013R2
 
KB4284833 OS Build 14393.2339 Windows Server 2016 BT2016
KB4338419 KB4338605 .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 and 4.7.2 Windows 8.1, RT 8.1, and Server 2012 R2 BT2016
KB4338814 OS Build 14393.2363 Windows 10,  (but also reported on Windows Server 2016 on twitter/technet) BT2016
KB4345418 OS Build 14393.2368 Windows Server 2016 BT2016
 
Also reported but probably not an issue
KB4338613 .NET Framework 3.5 SP1 Windows 8.1, RT 8.1, and Server 2012 R2
KB4338614 ? Probably a Typo for 4338814, as does not exist
KB4338424 NET Framework 3.5 SP1 Windows Server 2016 BT2016

The CVE’s in question which these KBs are addressing are:

Microsoft has published a blog post Advisory on July 2018 .NET Framework Updates and the following KB about the issue. “Access Denied” errors and applications with COM activation fail after installing July 2018 Security and Quality Rollup updates for .NET Framework

BizTalk 2016 – Feature Pack 3 & CU5

Feature Pack 3 with CU5

Important Note: Don’t mix Feature Packs and CUs as per BizTalk 2016 Feature Pack vs BizTalk 2016 CUs

Note: This has been replaced with Feature Pack with CU8, and soon Feature Pack with CU9 will be available

Microsoft have released Feature Pack 3 which you can download from here, details of all the feature packs are on Microsoft Docs.

This Feature Pack includes 3 new adapters

As usual it also includes the latest cumulative update in this case CU5.

Further reading for this BizTalk Server 2016 Feature Pack 3 is publicly available, and I have to try it!

BizTalk 2016 CU5

Additional requirements

  • The TLS 1.2 Support has a prerequisite of SQL Server 2012 Native Client version 11 that you must install, otherwise the CU / FP will fail to install

SQL Server 2012 Native Client version 11 should be installed on all BizTalk Server systems before you apply this update. If the SQL Native Client is not installed before you apply cumulative update, the installation may not complete.

https://support.microsoft.com/en-nz/help/4091110/support-for-tls-1-2-protocol-in-biztalk-server

If you use the MQSeries adapter you must run the CU on the IBM Websphere server, and this also needs to SQL Server 2012 Native Client version 11, see Sandro Pereira’s blog post BizTalk Server 2016 CU5 Installation error: SQLNCLI11 ole db


Note If you use the MQSeries adapter, MQSAgent.dll must be updated on the IBM WebSphere MQ server to the same cumulative update level that’s on BizTalk Server. To do this, make sure that you run the same cumulative update setup on the IBM WebSphere MQ server. You may experience performance issues if you run mismatched versions.

https://support.microsoft.com/en-nz/help/4132957/cumulative-update-5-for-microsoft-biztalk-server-2016

Important You must install WinSCP version 5.13.1 after you install this cumulative update.

https://support.microsoft.com/en-nz/help/4087345/sftp-adapter-improvements-for-biztalk-server

Fixes

Details of CU5 can be found here, apart from the usual minor fixes to the FTP, SAP/iDoc it has a few others which I find more interesting.

Orchestration is unbound and pipeline settings are lost when redeploying a Visual Studio project in BizTalk Server   I’m sure this one will be pleasing to most developers as this was an annoyance for several version of BizTalk development.

Support for TLS 1.2 protocol in BizTalk Server  This was initially released as part of Feature Pack 2, and not as part of a CU, so non-enterprise BizTalk 2016 servers couldn’t get this, now they can.

Support added for SQL Server 2016 Service Pack 2 in BizTalk Server 2016 Microsoft SQL Server 2016 Service Pack 2 (SP2) is added to the list of supported platforms for Microsoft BizTalk Server 2016 starting in Cumulative Update 5 (CU5).

Cumulative Update package 8 for BizTalk Server 2013 R2

Microsoft has released CU 8 for BizTalk Server 2013 R2, details here 

  • Two fixes for WCF-SAP / NCO SAP.
  • Two fixes for MSMQ series
  • One for HTTP Port
  • Support for TLS 1.2 protocol, so you can disable earlier versions of TLS (as long as all the end points you connect to also support it).
  • One fix for BAM Alerts.

 

Cumulative Update package 7 for BizTalk Server 2013 R2

Microsoft have just released CU 7 for BizTalk 2013 R2

These CU includes 6 fixes.

I got rather excited when I saw that they had fixed an issue with the WCF-SQL adapter polling.  However the cases the symptoms they describe aren’t quite the same as one we’ve encountered in BizTalk 2010 (so I don’t think this fix is going to help us even when do they get around to patching other BizTalk version).  But it may fix things for others or spur them to look a bit closer at this adapter to fix other issues.

As per nearly every CU, it contains a iDoc/SAP/NCo fix and one for EDI.

There are also two fixes for two-way send ports (one deployment issue and the other a runtime one), and finally a TDDS/database fix.

 

Mike the Tester

A blog about all things testing. Views are my own

Nick's Blog

Biztalk gotcha!

Whatever

FURIOUSLY REASONABLE

A Different Kind of Query

Technology, music, life, and musings

Vierodan IT Space

Spread up technology

BizTalk Server Help book!

Made easy and simple

nethramysooru

Blog on BizTalk Server

Blog Of the Serverless Spirit

Stray Notions on All Things Microsoft Azure and BizTalk

Microsoft Azure/BizTalk_Read

Let's learn and share !

Boutaleb Hicham

Biztalk & Azure Integration Architect : Logic Apps, Serverless, Azure Service Bus, BizTalk Server, and Hybrid Integration

Pieter Vandenheede

Stories, tips & tricks for BizTalk Server, Azure, Data Science & Machine Learning

Glenn Colpaert

Blogging with my head in the (Hybrid) Cloud and my feet on premises! Azure / IoT / Integration

BizMunch

BizTalk blog by Knut Urke

Dragon's BizTalk Blog

A blog about BizTalk, and other integration tools.

The Deployment Bunny

OS Deployment, Virtualization, Microsoft based Infrastructure...

Integration Made Easy

Demystify Integration Development