Some of you might be wondering why Microsoft BizTalk 2013 CU5 now, right? Well, let me tell you that even though many of you may have recently acquired the new Microsoft BizTalk 2016 CU which of course has come with plenty of benefits. For example support for newer platforms: Visual Studio 2015, Windows Server 2016, SQL Server 2016 and Office 2016, to name a few. Many of our clients are still using the Microsoft BizTalk Server 2013, and we assist you as well.
The Cumulative update package 5 for BizTalk Adapter Pack 2013 covers hotfixes for BizTalk Adapter Pack 2013, complications that were repaired following the release of BizTalk Adapter Pack 2013. It is suggested that the hotfixes be tested before they are launched. Every cumulative update package incorporates all component updates, nevertheless, the cumulative update package updates only those components that are installed on the system, and therefore it is recommended to use the most recent BizTalk Adapter Pack 2013 update.
For more information about the BizTalk Adapter Pack 2013 issues click the following article numbers to go to the articles in the Microsoft Knowledge Base.
|KB article number||Description|
|3192680||FIX: NCO BAPI response structure is different from ClassicRFC when BAPI response is empty|
|3202537||FIX: “Error occurred while browsing the LOB system” when you expand IDOC schema with new NCo connector type in BizTalk Server|
|3203865||FIX: BizTalk Data Provider for SAP does not have the ConnectorType property|
|4010116||FIX: “Unable to allocate client in pool” error in NCo in BizTalk Server|
|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|
|4020013||FIX: iDOC received in SAP is missing the segment hierarchy and contains errors when it is sent through NCo from BizTalk Server|
|4020014||FIX: SAP adapter in NCo mode does not trim trailing non-printable characters in BizTalk Server|
How to obtain the BizTalk 2013 CU5 Adapter Pack
The latest fixes are openly released in the upcoming cumulative update. However, if there are critical reported problems, that have major business collision, and do not have a workaround, single fixes may be delivered preceding the next cumulative update, and if provided, they require the latest released cumulative update as a prerequisite.
Click here to download the BizTalk 2013 CU5 Adapter Pack
To discover more on BizTalk visit this page and please comment your thoughts with us.