SAP troubleshooting guide

Use this guide to troubleshoot issues when you set up the SAP connector. If the issue you encounter isn't listed here, check the agent.log file or contact Workato Support (opens new window).

Enable debug logging

We recommend that you enable debug logging in your config.yml file if you experience issues when you set up the SAP RFC connector. This enables you to capture detailed error information during connection attempts. For example:

logging:
  workato.sap.adapter: DEBUG

Refer to the Common issues and Error messages sections to identify and resolve problems.

Common issues

You may encounter the following issues when setting up or connecting to SAP with a Workato on-prem agent:

Agent fails to start

The agent may display the following error during startup:

JCo initialization failed with java.lang.UnsatisfiedLinkError: C:\Program Files\Workato Agent PROD\lib_ext\sapjco3.dll: Can't find dependent libraries

On Windows platforms, JCo 3.1 requires you to install the Microsoft Visual Studio 2015-2022 C/C++ runtime libraries on your agent server. If these libraries aren't present, you must download and install the latest Microsoft Visual C++ 2015-2022 Redistributable Package from the Microsoft knowledge base article (opens new window). Select the package that matches your locale and JVM bit-width (x64 for 64-bit operating systems or x86 for 32-bit operating systems).

Agent fails to connect to SAP

Check the OPA logs to find the specific error. Learn how to enable debug logging.

IDocs missing from dropdown list

You must configure the required IDoc in your SAP system before Workato can display them in a drop-down list.

By default, Workato refreshes IDoc metadata every 24 hours. To change this interval, set metadata_refresh_interval in the SAP connection profile.

Contact Customer Success (opens new window) if the issues continue.

SAP RFC fails to call Workato APIs

Your SAP system configuration may not support TLS 1.2, which is required for incoming connections to Workato. Enable TLS 1.2 support in your SAP environment to complete the connection. Refer to the Configure SAP to interact with the Workato API platform guide for setup instructions.

Error messages

You may encounter the following errors when establishing a SAP connection. Use this section to identify the cause and resolve the issue.

java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path

This error occurs when the agent uses a Java connector package that doesn't match the host operating system. Ensure that you download and install the correct SDK version.

On macOS, the agent raises this error if libsapjco3.dylib doesn't exist in the lib_ext folder.

Classpath entry lib/sap-connector-X.X.X.jar not found, skipped.

This error appears on macOS when the sap-connector-X.X.X.jar file is moved to the lib_ext folder. To avoid classpath issues, keep the file in its default location.

Registration of tp <Program's name> from host ??? not allowed

This error may indicate issues in the reg_info or sec_info files. Follow SAP note 1850230 (opens new window) and complete the following steps to resolve it:

1

Move or rename the reginfo and secinfo files.

2

Confirm the OS-level path matches the values gw/reg_info and gw/sec_info in RZ11.

3

Set the value of the gw/reg_no_conn_info parameter to 0.

4

Set the value of the gw/acl_mode parameter to 0.

5

Ensure the SAP server (gwhost) is accessible from the agent host. Ping the server's IP address from Terminal or Command Prompt to verify connectivity.

java.lang.NoClassDefFoundError: com/sap/conn/jco/JCoException

This error occurs when the SAP Java Connector (JCo) library is missing or not correctly referenced in the agent classpath. Complete the following steps to resolve this:

1

Download the SAP JCo libraries that match your operating system. For example, download the Windows version if the agent runs on Windows. Refer to the SAP Java Connector (opens new window) page for more information.

2

Add the following files to the lib_ext folder in the Workato agent's home directory:

• sapjco3.jar
• sapjco3.dll (Windows), libsapjco3.so (Linux), or libsapjco3.dylib (macOS)
• sap-connector-impl-<version>.jar

3

Verify that the config.yml file includes lib_ext in the classpath. For example:

server:
  classpath:
    - lib_ext

4

Ensure proper indentation and formatting in your config.yml. Check the YAML indentation in your config.yml. If the formatting is incorrect, the agent may fail to load the SAP profile. For example:

Proper file indentation

Cannot invoke "com.workato.agent.sap.impl.json.IDocTypeBean.getSegMap()" because "selected" is null

This error occurs when the agent creates a trigger before it completes metadata retrieval from SAP. Wait 90 seconds for the OPA to retrieve the metadata.