Just installed CA LDAP Server for Compliance Event Manager, and when it starts it immediately ends . What would cause this?

Products

• Compliance Event Manager

Issue/Introduction

Just installed CA LDAP Server for Compliance Event Manager, and when it starts it immediately ends. What would cause this?

Environment

Release:
Component: CEVM

Resolution

The most common cause to the CA LDAP Server immediately ending or ending with a RC 256 when starting is a syntax error or invalid parameter in the slapd.conf or slapd.env files.

The CA LDAP Server may immediately terminate or terminate with a RC 256 when starting if there are parameter errors in the CA LDAP configuration slapd.conf or slapd.env files.

Parameter errors include the following.

Invalid parameter syntax.
Duplicate entries for parameters that require unique values.
Extraneous line numbers at the end of parameters.
Missing required parameters(slapd.conf parameters must start in column 1)

To identify possible parameter errors, start the CA LDAP Server with DEBUG. For example from the z/OS console:

S LDAPserver,DEBUG=ANY where LDAPserver is you CA LDAP Server Started Task Name

After CA LDAP Server fails with the RC 256 review the stderr file in the CA LDAP Server installation directory and check for error messages related to the slapd.conf or slapd.env files. If there are no obvious errors please contact CA Support and provide the following.

The CA LDAP Server Joblog.
The slapd.conf file.
The slapd.env file.
The stderr file.
Start LDAP Sever with debug, ie. s LPSERVE,debug=any , and send it the stderr log from the LDAP Server installation USS directory.