Home > ldap error code 65 object class violation

How do I fix LDAP error code 65 - object class violation?

Published on April 13th, 2022

The LDAP error code 65 occurs when an attempt is made to add an object to the LDAP server that violates the object class rules that are defined for that server. This can happen if the object being added has an attribute that is not allowed by the object class, or if the object being added is missing a required attribute.

1. Check that the object class is specified correctly in the LDIF file

  1. Verify that the object class is specified correctly in the LDIF file.
  2. If the object class is not specified correctly, then the LDIF file will contain an error code 65 object class violation.

2. Check that the object class is specified correctly in the schema

  1. Check that the object class is specified correctly in the schema.
  2. Check that the object class is not a system class.
  3. Check that the object class is not a user class.
  4. Check that the object class is not a directory class.
  5. Check that the object class is not a role class.
  6. Check that the object class is not a container class.
  7. Check that the object class is not a leaf class.
  8. Check that the object class is not a sequence class.
  9. Check that the object class is not a map class.
  10. Check that the object class is not a composite type.

3. Check that the object class is specified correctly in the configuration

There are three basic steps that must be followed in order to check that the object class specified in the configuration is correct:

  1. Verify that the object class is specified in the correct container.
  2. Verify that the object class is specified in the correct domain.
  3. Verify that the object class is specified in the correct schema.

4. Check that the object class is specified correctly in the code

  1. Verify that the object class is specified correctly in the code.
  2. Verify that the object class is specified in the LDAP schema.
  3. Verify that the object class is registered with the LDAP server.

5. Check that the object class is specified correctly in the documentation

  1. Verify that the object class is specified correctly in the documentation.
  2. Check the syntax of the object class definition.
  3. Check that the object class is a valid ldap class.
  4. Check that the object class has the correct permissions.
  5. Check that the object class has the correct naming schema.

Some users might also have success with the following opitons:

  1. Check that the object class is specified correctly in the UI.
  2. Check that the object class is specified correctly in the help.
  3. Check that the object class is specified correctly in the installation.