My Oracle Support Banner

Siebel 24.12: Receiving The Error ─ SBL-EAI-05006: Failed to load the JVM Dll. Check that the specified dll name is correct (Doc ID 3080445.1)

Last updated on APRIL 07, 2025

Applies to:

Siebel CRM - Version 24.12 and later
Information in this document applies to any platform.

Symptoms

On : 24.12 version, Siebel EAI

When attempting to invoke the JMS receiver to pick a message from the configured queue, the following error is encountered.

ERROR:
▬▬▬▬

ObjMgrBusServiceLog   Error   1   0000000d67ec6ec6:0  2025-04-02 03:43:40 (javabsvc.cpp (447)) SBL-EAI-05006: Failed to load the JVM DLL. Check that the specified dll name is correct.

STEPS:
▬▬▬▬
The issue can be reproduced at will with the following steps:

1) Update the 'JVMSubsys' parameter value of the *JMSReceiver* component to 'JAVA64' using the following command:

    Reference Document:

     Setting Up And Using JAVA64 Named Subsystem For Siebel EAI JMS Transport (Doc ID 2332726.2) 

       ↳ 3b. Siebel JAVA64 (64 bit) - IP17

           ↳ Step 6: Execute the following command.

change parameter JVMsubsys=JAVA64 for component JMSReceiver;  where JMSReceiver will access the JMS Server to receive messages

2) Configure the JAVA64 Profile – CONTAINERURL value by following:

    Reference Document:

      Setting Up And Using JAVA64 Named Subsystem For Siebel EAI JMS Transport (Doc ID 2332726.2)

        ↳ 3. Siebel Application Side Setup

            ↳ 3b. Siebel Application Side Setup - JAVA64 (64 bit) - IP17

                ↳ Step 5: Create the JAVA64 profile: CONTAINERURL

Parameter section: the CONTAINERURL value is populated by default out of the box. Double check it uses http, localhost, and the correct/chosen SES HTTP PORT number during SES installation.

3) Set the CLASSPATH parameter for the JAVA64 profile:

    ◙ Update the 'CLASSPATH' parameter in the JAVA64 named subsystem to point only to the location of the 'jndi.properties' file.
    ◙ Do not list any '.jar' files in this value.

 Note: the CLASSPATH parameter for the Siebel JAVA64 named subsystem must end with :. on Unix.

   Reference Document:

     Setting Up And Using JAVA64 Named Subsystem For Siebel EAI JMS Transport (Doc ID 2332726.2)

       ↳ 3. Siebel Application Side Setup 

          ↳ 3b. Siebel Application Side Setup - JAVA64 (64 bit) - IP17

              ↳ Step 5: Create the JAVA64 profile: CLASSPATH

4) Place all custom 3rd-party JARs into the location mentioned below.

NOTE: From Siebel 21.2 onwards, copy the 3rd party jars into the /ses/applicationcontainer_internal/webapps/siebel/WEB-INF/lib directory.

    Reference Document:

      Where To Put 3rd Party Jar Files For Siebel Java Business Service and JMS Transport When Using IP17+ JAVA64 Subsystem? (Doc ID 2648687.1)

5) Restart all Siebel services to apply the changes and re-execute the test case to verify whether the error has been resolved.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References


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