Products | Versions |
---|---|
TIBCO ActiveMatrix BusinessWorks Plug-in for Files for Unix and Windows | - |
Not Applicable | - |
Description:
Adapter on Windows throws the error, "Startup error. SDK Error: Could not open JMS shared library jms, DllError.". Then a pop-up is seen with the following message, "The ordinal 3823 could not be located in the dynamic link library LIBEAY32.dll".
Symptoms:
TIBCO ActiveMatrix Adapter for Files for Unix/Win (FA) throws the error, "Startup error. SDK Error: Could not open JMS shared library jms, DllError.". Then a pop up is seen with the following message, "The ordinal 3823 could not be located in the dynamic link library LIBEAY32.dll".
Cause:
The error is due to a conflict that is occurring between the LIBEAY32.dll and SSLEAY32.dll that is used by TIBCO products such as RV/JMS/HAWK and some non TIBCO products. TIBCO Rendezvous (RV) 7.2+, TIBCO Enterprise for JMS (JMS) 3.1.1+ and TIBCO Runtime Agent (TRA) 5.1.2+ use OpenSSL code (files LIBEAY32.dll and SSLEAY32.dll). There are other applications which use the above OpenSSL code and hence, on some machines, LIBEAY32.dll and SSLEAY32.dll are already installed by non TIBCO applications in C:\Windows\system32.
When TIBCO Java applications are started, the JVM looks for a property called java.library.path that specifies native library paths. If java.library.path is not set explicitly, then the JVM sets the value of java.library.path to the environment variable PATH but prepend C:\Windows\System32 and other directories. If the versions of LIBEAY32.dll and SSLEAY32.dll in C:\Windows\system32 are not compatible with TIBCO Rendezvous, TIBCO applications may fail when trying to use TIBCO Rendezvous or TIBCO JMS.
- If you have RV 8.1 installed in <TIBCO_HOME>/tibrv/8.1, copy the latest files from the ./tibrv/8.1/bin folder to the .\<Windows_HOME>\System32 folder and to the <TIBCO_HOME>/adapter/sdk/<version>/bin folder.