< class="prominent-subhead ">

K2 Connect Administration tools return "Connection test failed. Cannot call NetWeaver RFC API" error.

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


After installing K2 Connect, the K2 Connect Administration tool starts showing a "Connection test failed. Cannot call NetWeaver RFC API" error screen.



Notes: SAP ended support for the Classic RFC libraries on 31 March 2016 after which SAP only supports the SAP NetWeaver RFC libraries. The new dlls are not redistributable from SourceCode Technology Holdings, Inc and must be obtained from http://service.sap.com/.  

Once downloaded the new NetWeaver RFC libraries must be copied to the respective system folders. The zip files for each architecture (64 and 32 bit) will contain six files. All six files need to be copied:

  • icudt34.dll
  • icuin34.dll
  • icuuc34.dll
  • libicudecnumber.dll
  • libsapucum.dll
  • sapnwrfc.dll

The 32bit files go to c:\Windows\SysWOW64.

The 64bit files go to c:\Windows\System32.

Troubleshooting Steps

1. Verify that the six dlls for the SAP Netweaver RFC Libraries are going to the following location:

  • For 32-bit machines - C:\Windows\SysWOW64.
  • For 64-bit machines - Copy the x64 SAP Netweaver RFC Libraries to the C:\Windows\System32 folder, and copy the x32 SAP Netweaver RFC Libraries to the C:\Windows\SysWOW64.

2. Restart the K2 Connect and K2 Server service.