Skip to content
DocumentationDocsBlogContact
← All field notes
BizTalk Era February 2, 2017 4 min read BizTalk

BizTalk 2016 CU1 – Download it here

  Microsoft has made available the BizTalk 2016 CU1, their popular integration engine. It’s loaded with several fixes for SAP, HTTP, MQSAgent and POP3. You can download it here   Here is the full list of fixes…

BizTalk 2016 CU1

 

Microsoft has made available the BizTalk 2016 CU1, their popular integration engine.

It’s loaded with several fixes for SAP, HTTP, MQSAgent and POP3.

You can download it here

 

Here is the full list of fixes included in BizTalk 2016 CU1.

[su_table]
[su_row]
[su_column size=”1/4″]KB article number [/su_column]
[su_column size=”3/4″]Description[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 3202533[/su_column]
[su_column size=”3/4″]FIX: MQSAgent2 delays or stops polling messages between Biztalk MQSeries adapter and MQ server[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 3202740[/su_column]
[su_column size=”3/4″]FIX: MQSeries adapter handles only one receive location at a time when ordered delivery is set in BizTalk Server[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 3203865[/su_column]
[su_column size=”3/4″]FIX: BizTalk Data Provider for SAP does not have the ConnectorType property[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 3202537[/su_column]
[su_column size=”3/4″]FIX: “Error occurred while browsing the LOB system” when you expand IDOC schema with new NCo connector type in BizTalk Server[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 3202535[/su_column]
[su_column size=”3/4″]FIX: The MIME/SMIME decoder in the POP3 adapter selects an incorrect MIME message part in BizTalk Server 2013 or 2016[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 3202534[/su_column]
[su_column size=”3/4″]FIX: The host instance stops when the HTTP send port times out in BizTalk Server[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 3121493[/su_column]
[su_column size=”3/4″]FIX: WCF-HTTP send doesn’t retry or suspend when it receives an error 500 in BizTalk Server[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 4010116[/su_column]
[su_column size=”3/4″]FIX: ‘Unable to allocate client in pool’ error in NCo in BizTalk Server[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 4010119[/su_column]
[su_column size=”3/4″]FIX: NullReferenceException error when you use the Windows SharePoint Services adapter to access SharePoint Online[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 4010115[/su_column]
[su_column size=”3/4″]FIX: “400 Bad Request” error when you send an email message to SharePoint that is larger than 2 MB[/su_column]
[/su_row]
[/su_table]

BizTalk Server Message Runtime, Pipelines, and Tracking

[su_table]
[su_row]
[su_column size=”1/4″]KB article number[/su_column]
[su_column size=”3/4″] Description[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 4010117[/su_column]
[su_column size=”3/4″]FIX: “TimeStamp retrieval failed” error in BizTalk Server when an FTP server responds with milliseconds[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 3194293[/su_column]
[su_column size=”3/4″]Orphaned BizTalk DTA service instances are not removed by the “DTA Purge and Archive” job in BizTalk Server[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 4010248[/su_column]
[su_column size=”3/4″]FIX: Inadequate error message when the receive pipeline fails because 32-bit A4HL7 is running on 64-bit BizTalk Server 2016[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 4010249[/su_column]
[su_column size=”3/4″]FIX: BTARN error message is too general to help find the root cause of the RNIF error[/su_column]
[/su_row]
[/su_table]

 

BizTalk Server Administration Tools and Management APIs

[su_table]
[su_row]
[su_column size=”1/4″] KB article number[/su_column]
[su_column size=”3/4″] Description[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 4010407[/su_column]
[su_column size=”3/4″]FIX: The selected node for a schema is not highlighted in the BizTalk Editor in Visual Studio 2015[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 4010327[/su_column]
[su_column size=”3/4″]FIX: Configuration fails at the BAM portal in BizTalk Server 2016[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 3202894[/su_column]
[su_column size=”3/4″]FIX: You cannot change the Tracking QueryTimeout value when you use BizTalk Server 2013 or 2016[/su_column]
[/su_row]
[su_row]
[su_column size=”1/4″] 4010118[/su_column]
[su_column size=”3/4″]BizTalk Server 2016 is Drummond certified for SHA-2[/su_column]
[/su_row]
[/su_table]

 

As we’ve done before, we advise installing this Cumulative Update 1 for BizTalk 2016 in a secure environment and testing it before moving these changes to production servers.

NOTE Each cumulative hotfix package includes all the component packages. However, a cumulative update package updates only those components that are installed on the system.