Why does the TIBCO Adapter (TM) for LDAP throw the error “The Ordinal 3212 could not be located in the dynamic link library LIBEAY32.dll” error while trying Design Time Connection?

Why does the TIBCO Adapter (TM) for LDAP throw the error “The Ordinal 3212 could not be located in the dynamic link library LIBEAY32.dll” error while trying Design Time Connection?

book

Article ID: KB0092345

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for LDAP -
Not Applicable -

Description

Resolution:
This error is due to the conflict that is occurring between the LIBEAY32.dll and SSLEAY32.dll that is used by TIBCO products like RV/JMS/HAWK and some NON TIBCO product.

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 too 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, then TIBCO applications may fail when trying to use TIBCO Rendezvous (or TIBCO JMS).

Resolution:

Remove/Replace/Rename the two dlls LIBEAY32.dll and SSLEAY32.dll that present in C:\Windows\System32 with that present in TIBCO_RV_HOME\bin

Issue/Introduction

Why does the TIBCO Adapter (TM) for LDAP throw the error “The Ordinal 3212 could not be located in the dynamic link library LIBEAY32.dll” error while trying Design Time Connection?