Where can I download the LIBRFC32.DLL or the SAP NetWeaver RFC DLLs and how can I install them?

 

Description

You open SmartExporter and test the SAP® connection and an error message is displayed that, for example, a problem occurred with “LIBRFC32.DLL”.

To communicate with an SAP® system SmartExporter either requires the classic RFC DLL “LIBRFC32.DLL” or uses SAP NetWeaver® RFC DLLs.

Due to legal reasons only the SAP NetWeaver® RFC-DLLs can be included in the SmartExporter deployment. (See „License Terms for SAP Connectors“ section at https://support.sap.com/en/product/connectors.html#section_561121760.) For SmartExporter 2024 R1 and higher, the NetWeaver RFC DLLs are included in the SmartExporter setup and are automatically copied to the correct directory during installation. This means that you do not have to perform any manual steps when using the NetWeaver® RFC protocol.

However, the classic RFC DLL cannot be deployed in the SmartExporter setup. So if you want to use the classic RFC protocol, you may first have to download the classic RFC DLL and copy it to the correct directory. Please see the detailed instructions below.

Note: 

Since 31 March 2016 the classic RFC DLL has no longer been officially supported by SAP®. However, SmartExporter still runs with the versions specified in the instructions below.

 

Solution

The instructions of how to proceed to solve the problem depend on whether you are using SmartExporter in combination with IDEA.

Do you use SmartExporter in combination with IDEA?

 

-- Please select the appropriate value from the selection field above! --

How to proceed when using the Classic RFC DLL and IDEA 11.1 or higher

Follow the steps described below:

  1. Make sure that in SmartExporter the classic RFC DLL is selected for the communication. You can specify this setting in the Options group in the Change application options entry in the Communication entry.

  2. Now you have to download the required RFC DLL, decompress it and copy it to the correct directory. If you are a registered user with SAP®, you can download the RFC DLL “LIBRFC32.DLL” from the SAP® for Me SAP® portal.

    Please select the correct file: RFC_13-10009731.SAR (Version 7200.0.800.8330)

  3. Decompress the SAR files using the SAP® tool SAPCAR with the parameter -xvf.

    Example: SAPCAR_712-80000936.EXE -xvf RFC_13-10009731.SAR

    Regarding SAPCAR see SAP® Note 212876.

    You find the “LIBRFC32.DLL” in the “rfcsdk\lib” directory.

  4. Copy the 64 bit version of the "LIBRFC32.DLL" file to "C:\Windows\System32".

 

Note:

- If the "LIBRFC32.DLL" of the SAP® version 7400 is used, the error message "Cannot call classic RFC API..." may be shown when establishing the connection. Therefore please select the .SAR file specified above.

 

How to proceed when using the Classic RFC DLL (without IDEA)

Follow the steps described below: 

  1. Make sure that in SmartExporter the classic RFC DLL is selected for the communication. You can specify this setting in the Options group in the Change application options entry in the Communication entry.

  2. If you are a user registered with SAP®, you can download the RFC DLL from the SAP® for Me SAP® portal.

    Please select the correct file:

  3. Decompress the SAR files using the SAP® tool SAPCAR with the parameter -xvf.

    Example: SAPCAR_712-80000936.EXE -xvf RFC_13-10009731.SAR

    Regarding SAPCAR see SAP® Note 212876.

    You find the “LIBRFC32.DLL” in the “rfcsdk\lib” directory.

  4. In the last step you have to copy the DLL file to the correct directory:

    • Copy the 64 bit version of the "LIBRFC32.DLL" file to "C:\Windows\System32".

 

Note:

- Please note that there are different "LIBRFC32.DLL" files for 32 bit and 64 bit Windows operating systems, despite the fact that they have identical names!

- If the "LIBRFC32.DLL" of the SAP® version 7400 is used, the error message "Cannot call classic RFC API..." may be shown when establishing the connection. Therefore please select one of the two .SAR files specified above.