CU Package 4 BizTalk Adapter Pack 2013
This cumulative update for BizTalk Adapter Pack 2013 contains hotfixes for BizTalk Adapter Pack 2013 issues that were fixed after the release of BizTalk Adapter Pack 2013.
We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included in the previous BizTalk Adapter Pack 2013 update release. We recommend that you consider applying the most recent BizTalk Adapter Pack 2013 update.
Important notes about the cumulative update package
- Every cumulative update package includes all component updates. However, the cumulative update package updates only those components that are installed on the system.
Note For more information about the latest service pack or cumulative update package for BizTalk Adapter Pack 2013, click the following article number to go to the article in the Microsoft Knowledge Base:
More Information
A cumulative update package for BizTalk Adapter Pack 2013 is a rollup update that contains all previous hotfixes to date for BizTalk Adapter Pack 2013.
For more information about the terminology that is used to describe Microsoft product updates, click the following article number to go to the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates
Hotfixes that are included in cumulative update package 4 for BizTalk Adapter Pack 2013
The Microsoft Knowledge Base articles that discuss these hotfixes are released as they become available. 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 |
|---|---|
| 3162562 | FIX: SAPBinding constructor fails with NullReferenceException |
| 3164725 | FIX: IDOCs sent with BizTalk WCF-SAP NCO adapter are misaligned in SAP |
| 3164728 | FIX: WCF-SAP NCO adapter fails when saprfc.ini file contains comments in BizTalk Server |
| 3164730 | FIX: NullReferenceException is thrown when you change ConnectorType on WCF-SAP send port in BizTalk Server |
| 3189028 | FIX: IDOCs sent with BizTalk WCF-SAP NCO adapter trigger aSyntax or Missing Segment error in SAP |
| 3192680 | FIX: NCO BAPI response structure is different from ClassicRFC when BAPI response is empty |
| 3197184 | WCF-SAP Nco Connector creates additional white spaces in BizTalk Server 2013 |
| 3194304 | Intermittent “Invalid destination NCoConnection (DELETED)” error messages when a SAP Send port makes an RFC call to get open items |
How to obtain cumulative update package 4 for BizTalk Adapter Pack 2013
BizTalk Server uses a cumulative update (CU) model for providing fixes and updates. Each cumulative update includes new updates as well as all of the updates included in the previous cumulative updates. We recommend that you test and apply the latest CU to all BizTalk environments.
All new fixes are publicly released in the upcoming cumulative update. Stand-alone fixes may be provided prior to the next cumulative update if the reported problem is critical, has significant business impact, and does not have a workaround. Stand-alone fixes (if provided) require the latest released cumulative update as a prerequisite.
Download Center
The following file is available for download from the Microsoft Download Center:
Release Date: October 10, 2016
For more information about how to download Microsoft support files, see how to obtain Microsoft support files from online services .
Cumulative update package information
Prerequisites
To apply this cumulative update package, you must have BizTalk Adapter Pack 2013 installed.
Note If a Readme.txt file is included in this cumulative update package, see the Readme.txt file for more information about how to install this update.
Restart requirement
You have to restart the computer after you apply this cumulative update package.
References
For more information about BizTalk Server hotfixes, click the following article number to go to the article in the Microsoft Knowledge Base: