|
 OpenLDAP Faq-O-Matic : OpenLDAP Software FAQ : Common Errors :
 ldap_add/modify: Object class violation |
This error is returned with the entry to be added or the entry
as modified violates the object class schema rules. Normally
additional information is returned the error detailing the
violation. Some of these are detailed below.
- Violations related to the entry's attributes:
- Attribute not allowed
- A provided attribute is not allowed by
the entry's object class(es).
- Missing required attribute
- An attribute required by the entry's object class(es) was not provided.
- Violations related to the entry's class(es):
- Entry has no objectClass attribute
- The entry did not state which object classes it belonged to.
- Unrecognized objectClass
- One (or more) of the listed objectClass values is not recognized.
- No structural object class provided
- None of the listed objectClass values is structural.
- Invalid structural object class chain
- Two or more structural objectClass values are not in
same structural object class chain. See also
 ldap add: invalid structural object class chain.
- Structural object class modification
- Modify operation attempts to change the structural class of the entry.
See also ldap_modify: cannot modify object class.
- Instanstantiation of abstract objectClass.
- An abstract class is not subordinate to any listed structural
or auxiliary class.
- Invalid structural object class
- Other structural object class problem.
- No structuralObjectClass operational attribute
- This is commonly returned when a shadow server is provided an entry which does not contain the structuralObjectClass operational attribute.
|
Note that the above error messages as well as the above answer assumes basic knowledge of LDAP/X.500 schema.
|
| [Append to This Answer] |