CA LDAP Server starts and immediately ends with COND CODE 0009 and no error messages, why?
Article ID: 128825
Updated On:
Products
ACF2
ACF2 - DB2 Option
ACF2 for zVM
ACF2 - z/OS
ACF2 - MISC
Issue/Introduction
CA LDAP Server starts and immediately ends with COND CODE 0009 and no error messages, why?
Environment
Release:
Component: ACFLDP
Component: ACFLDP
Resolution
The stderr was not readable because it was in ascii format. When converting the stderr to EBCDIC there were two lines in the stderr:
CEE3501S The module libslapd.dll was not found.
The traceback information could not be determined.
The libslapd.dll exists in the CALDAP Server directory. To resolve the problem verify that the libslapd.dll exists in the CA LDAP installation directory that is pointed to by the sladp.env LIBPATH and PATH variables. If the LIBPATH is incorrect the stderr file will default to ascii format rather than EBCDIC.
If the libslapd.dll cannot be found, the stderr file will be in ascii format and the server will end with cond code 9.
CEE3501S The module libslapd.dll was not found.
The traceback information could not be determined.
The libslapd.dll exists in the CALDAP Server directory. To resolve the problem verify that the libslapd.dll exists in the CA LDAP installation directory that is pointed to by the sladp.env LIBPATH and PATH variables. If the LIBPATH is incorrect the stderr file will default to ascii format rather than EBCDIC.
If the libslapd.dll cannot be found, the stderr file will be in ascii format and the server will end with cond code 9.
Feedback
Yes
No
Powered by
