Phidiax Tech Blog

Adventures in custom software and technology implementation.

BizTalk 2013 R2 CU2 causes WCF-SAP adapter failure - sapnco - System.IO.FileNotFoundException Could not load file or assembly

Recently, after updating BizTalk 2013 R2 with Cumulative update package 2 for BizTalk Server 2013 R2 (CU2), the WCF-SAP adapter failed to operate successfully. This is particularly concerning, especially in Production scenarios, when we generally feel comfortable applying CU's. 

You will see an error similar to the following:

The undocumented issue is that CU2 actually enables BizTalk WCF-SAP adapter, sapBinding, compatibility with the SAP .NET Connector, while creating an additional binary dependency.

Here is more information on article number 3100811.

The SAP .NET Connector 3.0 must be downloaded from the SAP Marketplace and installed on all BizTalk nodes running the WCF-SAP adapter. This functionality can be seen via the sapBinding of the BizTalk WCF-SAP adapter.

It should also be noted that the latest Visual C++ 2010 Redistributable (or sp1) for both x86 and x64 is required for proper functionality. Here are some links:


Comments (2) -

  • SAP Program Manager

    5/23/2016 7:50:13 AM | Reply

    Has this problem been fixed. One of our project had been using Microsoft BizTalk server and has issues in production. But not sure if it is related to this one. I will share this post with one of our IT architects.

    • Jason Sauers

      5/23/2016 8:20:41 PM | Reply

      You can check the CU on the PROD server, and compare to other working servers, if there are any.  CU2 is the start of this dependency. I submitted feedback to the BTS 2016 CTP so that hopefully this is fixed for later versions. However, I would assume for BTS 2013 and R2, you will encounter the dependency of NCO download from the SAP Marketplace. This is also assuming that you are dl'ing the RFC binaries, rather than installing the SAP Client. If working with the SAP client, you may sidestep this issue. Nevertheless, I like the least amount of binaries, so I would rather put in the elbow grease of working with the RFC.

      Let us know if we can help



Privacy Policy  |  Contact  |  Careers

2009-2017 Phidiax, LLC - All Rights Reserved