OIC SAP Adapter Connection - CASDK-0005: A connector specific exception was raised by the application. (Doc ID 2968607.1)

Last updated on AUGUST 17, 2023

Applies to:

Symptoms

Summary: While trying to establish a connection via the SAP adapter, we get a CASDK-0005 error that points to the JAR files in the $AGENT_HOME/thirdparty/lib directory. The agent is up and running on a Windows VM on-prem with the following files in the thirdparty/lib directory based on : https://docs.oracle.com/en/cloud/paas/application-integration/sap-adapter/add-jar-files-agent-class-path.html#GUID-F69758EC-2F59-4455-8CF1-8F222792A4AD

sapjco3.jar
sapidco3.jar
sapjoc3.dll

But the agent is throwing the following error:

[SRC Class: oracle.cloud.cpi.agent.transport.AQRuntimeConsumer$ProcessorTask; Method: run] CRITICAL: Receive failed with a Throwable exception. Please correct before trying again. Throwable : java.lang.ExceptionInInitializerError: JCo initialization failed with java.lang.UnsatisfiedLinkError: C:\oic_conn_agent_installer\agenthome\thirdparty\lib\sapjco3.dll: Can't find dependent libraries java.util.concurrent.ExecutionException: java.lang.ExceptionInInitializerError: JCo initialization failed with java.lang.UnsatisfiedLinkError: C:\oic_conn_agent_installer\agenthome\thirdparty\lib\sapjco3.dll: Can't find dependent libraries

Error from OIC UI
CASDK-0005: A connector specific exception was raised by the application. Probable causes: 1. If you were trying to connect SAP without Agent, one or more JCo libraries are missing or of incorrect version. Please make sure all the required JCo libraries are present in resource folder and all correspond to the same version. 2. If not, then Agent group is not configured.. Cause: Could not initialize class com.sap.conn.jco.rt.JCoRuntimeFactory

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.