Problem: The customer has MF COBOL installed on a machine where both dev1 and dev2 regions are running. The machine also has an OpenLDAP client installed. OpenLDAP server is running on another server. On this server, the user created a standard MF application containers and added default MFDS users, user groups and resources. When they added mldap_esm in Enterprise server as external security manager they are getting a connection error. SF0027E Error 16/101/4 SAFMGR initialization failed: Error reported by ESM Module Journal.txt show: 8301:4112513904 SA0203C ESM Module "LDAP" initialization failed (code 4) 8301:4112513904 SA1010E ESM1: Could not connect to LDAP server 8301:4112513904 SA1020E ESM1: Could not connect to LDAP Server at "camdv2lmfc01:389" and the ldapsearch command executed successfully from LDAP client to LDAP server: /usr/bin/ldapsearch -x -b 'dc=cammis-xerox,dc=com' -h camdv2lmfc01 -D "cn=admin,dc=cammis-xerox,dc=com" -w "0p3nld@p" schema.txt We did search if their client has any openldap directory, and the only place is in /lib64. /lib64/libldap-2.4.so.2 /lib64/libldap-2.4.so.2.5.6 /lib64/libldap_r-2.4.so.2 /lib64/libldap_r-2.4.so.2.5.6 Solution: As the above messages show, the ES attempted to connect to the LDAP server, and it failed. From the find command results that is used to locate openldap files on a Unix, it appears that the user only have the 64bit LDAP client libraries installed. If the DEV region is 32bit, then the LDAP libraries that we will call will need to be 32bit as well. After installing 32 bit openLDAP libraries, the user was able to connect LDAP server with openLDAP.
↧