[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: still unclear on error 69

Jon Roberts wrote:

Using OpenLDAP 2.1 and I'm running into an issue trying to extend an entry to include participation in new objectclasses (e.g. extending a person entry with objectclasses organizationalperson and inetorgperson). This used to work fine, but now I get an LDAP 69 error (object class mods prohibited). I noticed a post/response on this from last month:


but I fail to understand how the schema is involved, since all three of these classes are already represented. In other words, I have no earthly idea what I would do to the schema to make this work, and wouldn't want to modify a standard schema file in the first place.

Logical thinking: If what you had worked before and does not work any longer, what could possibly have changed in your setup to have altered this?

- have you changed your Openldap 2.1 version?
- have you had to reset your machine?
- have you had to reboot your machine?
- have you over strained/overloaded your installation?
- have you re indexed?


What database (bdb, ldbm) are you using? Version?
Could you have exceeded file size boundaries?
Could you have exceeded environment boundaries?

Does this mean there is no way to modify the objectclass attribute of an entry through the protocol without turning schema checking off?

You wouldn't want to do this, would you? Why have you never had to before?


Tony Earnshaw

Mail: tonni@billy.demon.nl