Just installed LDAP Server(for Compliance Event Manager/CA IdentityMinder) and when it starts it immediately ends with a RC 256. What would cause this?

Products

• LDAP SERVER FOR Z/OS

Issue/Introduction

Just installed LDAP Server(for Compliance Event Manager / IdentityMinder), and when it starts it immediately ends with a RC 256. What would cause this?

Resolution

The most common causes to the LDAP Server ending with a RC 256 when starting is a syntax error or invalid parameter in
the slapd.conf or slapd.env files or missing LDAP schema 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)

Missing CA LDAP schema files.

The core.schema or cosine.schema files are required LDAP Server files that must be in the LDAP installation directory.

Debugging

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

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

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

1. The LDAP Server Joblog. 
2. The slapd.conf file. 
3. The slapd.env file.
4. The stderr file.