Good news, Microsoft BizTalk Server 2016 CU2 is here and it’s ready to be of use.

Microsoft has released the CU2 for BizTalk Server 2016.

This means that it contains all the hotfixes and updates from the BizTalk Server 2016 release up until now, and this latest version is the one recommended.  It is also suggested that before its deployment in a production atmosphere, it first should be assessed as a test.

Some things to take into account to avoid performance issues when updating the hotfixes are: if you are currently using MQSeries adapter, then MQSAgent.dll necessarily has to be updated on the IBM WebSphere MQ server, and match the cumulative update level that of BizTalk Server.

For more information about the BizTalk Server issues, click the following article numbers to go to articles in the Microsoft Knowledge Base.

BizTalk Server Adapter

KB article number	Description
4010116	FIX: “Unable to allocate client in pool” error in NCo in BizTalk Server
4013857	FIX: The WCF-SAP adapter crashes after you change the ConnectorType property to NCo in BizTalk Server
4011935	FIX: MQSeries receive location fails to recover after MQ server restarts
4012183	FIX: Error while retrieving metadata for IDOC/RFC/tRFC/BAPI operations when SAP system uses non-Unicode encoding and the connection type is NCo in BizTalk Server
4013857	FIX: The WCF-SAP adapter crashes after you change the ConnectorType property to NCo in BizTalk Server
4020011	FIX: WCF-WebHTTP Two-Way Send Response responds with an empty message and causes the JSON decoder to fail in BizTalk Server
4020012	FIX: MIME/SMIME decoder in the MIME decoder pipeline component selects an incorrect MIME message part in BizTalk Server
4020014	FIX: SAP adapter in NCo mode does not trim trailing non-printable characters in BizTalk Server
4020015	FIX: File receive locations with alternate credentials get stuck in a tight loop after network failure

BizTalk Server Accelerators

KB article number	Description
4020010	FIX: Dynamic MLLP One-Way Send fails if you enable the “Solicit Response Enabled” property in BizTalk Server

BizTalk Server Design Tools

KB article number	Description
4022593	Update for BizTalk Server adds support for the .NET Framework 4.7

BizTalk Server Message Runtime, Pipelines, and Tracking

KB article number	Description
3194297	“Document type does not match any of the given schemas” error message in BizTalk Server
4020018	FIX: BOM isn’t removed by MIME encoder when Content-Transfer-Encoding is 8-bit in BizTalk Server

 

Commonly, new fixes are openly released within the next cumulative updates. However, repairs can be offered previous to the next update, if the issues are significantly urgent because the business upshot is large and there isn’t a transitory solution. If that’s the case, these “Stand-alone” fixes must essentially be updated with the most current cumulative update.

To download the BizTalk Server 2016 CU2 click here.

For more information about how to download Microsoft support files, see how to obtain Microsoft support files from online services.

To learn more about BizTalk visit this page and don’t forget to send us your comments.