Cumulative Update Package for BizTalk Server 2013 (CU5) and BizTalk Adapter Pack 2013 (CU4) is available


We are happy to announce two new Cumulative updates one for BizTalk Server 2013 (CU5) and BizTalk Adapter Pack 2013 (CU4) is available.

Cumulative update package 5 for Microsoft BizTalk Server 2013:

This cumulative update package for Microsoft BizTalk Server 2013 CU5 contains hotfixes for the BizTalk Server 2013 issues that were resolved after the release of BizTalk Server 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 Server 2013 update release. We recommend that you consider applying the most recent BizTalk Server 2013 update release.

  • All hotfixes that were released for BizTalk Server 2013, some hotfixes from BizTalk Server 2010 and general improvements to the product KB Articles included in this CU
    • 3142269 - FIX: Archive folder files are collected when you use a receive location to receive files from a SharePoint library
    • 2936805 - FIX: "Cannot insert the value NULL" error occurs when you use sequential convoy in BizTalk Server 2013
    • 3165515 - FIX: BizTalk HTTP send host crashes FireTransmitComplete during time-outs
    • 3194293 - Orphaned BizTalk DTA service instances are not removed by the "DTA Purge and Archive" job in BizTalk Server
    • 3194295 - MQSeries Adapter receive locations stop receiving messages after you install Cumulative Update 3 for BizTalk Server 2013
    • 3194297 - "Document type does not match any of the given schemas" error message after you apply Cumulative Update 4 for BizTalk Server 2013
    • 3167704 - FIX: Redeployment of schema referenced by maps fails after you install BizTalk Server
  • Download and read more here: Cumulative update package 5 for Microsoft BizTalk Server 2013

Cumulative update package 4 for Microsoft 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.

  • All hotfixes that were released for BizTalk Server 2013, some hotfixes from BizTalk Server 2010 and general improvements to the product
  • KB Articles included in this CU
    • 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
  • Download and read more here: Cumulative update package 4 for Microsoft Adapter Pack 2013

We will also remind you that BizTalk Server 2016 will go GA within this quarter of 2016. Please let us know if you have any questions.

Comments (4)

  1. Thanks for sharing this information team 🙂

    1. BizTalk Team says:

      Anytime! Let us know if there is anything we can do to make your day easier!
      - Tord

  2. Joshua Brown says:

    With BizTalk Adapter Pack 2013 (CU4); will Windows Server 2012 (Not R2) still be the highest version of the Microsoft Windows O/S that is supported?

Skip to main content