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

Products

• Batch Processor
• Compile QQF
• Data Compressor for DB2 for z/OS
• CA Unicenter NSM
• RC/Update for DB2 for z/OS
• DB2 TOOLS- DATABASE MISC
• Compliance Event Manager

Issue/Introduction

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

Environment

Release:
Component: GEN

Resolution

The most common causes to the CA 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 CA 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 CA LDAP Server files that must be in the CA LDAP installation directory.

Debugging

To identify possible parameter errors or missing schema files, 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 or missing schema files. If there are no obvious errors please contact CA Support and provide the following.

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