As a quick reminder, for BizTalk Developer Tools please also update/install version 220.127.116.11 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.
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 18.104.22.168 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.”
The new “Error Threshold” property disables the receive location on error. The receive location is disabled when the error threshold is exceeded. If the error threshold is set to 0, then the receive location is not disabled.
The exceptions that occur in the SFTP receive location is written to the event log. This helps you troubleshoot any issues that affect the receive location.
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.”
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.
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.
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.
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.