Get started Bring yourself up to speed with our introductory content.

Scenario 1: JCo is unable to find the RFCDSK API library

Misleading or even indecipherable exception messages seem to be the rule of the day when it comes to debugging JCo connector installation exceptions. This checklist by veteran Java expert Austin Sincock sets the record straight on a number of bewildering and headache-inducing exceptions.

Exception: Exception in thread "main" java.lang.ExceptionInInitializerError: JCO.classInitialize(): Could not load middleware layer '' JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [C:jcosapjcorfc.dll: Can't find dependent libraries]. java.library.path [C:WINDOWSSystem32;C:WINDOWS;c:devjco] at<clinit>(

Cause: This exception occurs when the RFC dynamic link library, librfc32.dll, cannot be found in the system path i.e. c:windowssystem32. This is an issue specific to the Windows platform, as the functions contained in librfc32.dll have been added to a different library on other platforms. As such, there is no librfc32.dll in the UNIX world.

Resolution: Extract librfc32.dll from JCo archive and copy it to the C:WindowsSystem32 directory. This file must be found somewhere within the system path. Because other SAP applications, such as SAPGUI, install versions of librfc32X.dll into C:WindowsSystem32, it is best to install the JCo version into that directory, as well.


 Home: Introduction
  Scenario 1: JCo is unable to find the RFCDSK API library in the system path
 Scenario 2: JCo is unable to find the JCORFC library in the system path
 Scenario 3: JCo cannot load its RFC middleware layer (3 exceptions)
 Scenario 4: JCo finds the wrong version of the librfc library
 Scenario 5: JCo exceeds the number of SAP-allocated work processes
 Scenario 6: Installing/porting JCo to other operating systems
 Review: Conclusion and more resources

Dig Deeper on SAP Basis

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.