RE: object class violation with ldapadd

["Howard Chu" <hyc@highlandsun.com>]

The current code may log an error on the server side (if you have debugging
enabled), but doesn't tell the client anything explicit. I'm working on a
patch to the 2.0 alpha base that will send more explicit error messages back
to the client for schema violations.

> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Jason Bodnar
> Sent: Monday, August 09, 1999 1:49 PM
> To: openldap-software@OpenLDAP.org
> Subject: object class violation with ldapadd
>
>
> Is there anyway to tell what the violation is when you get an
> "object class
> violation" using ldapadd?
>
> I did -v for verbose. It shows all the attributes it's adding and
> then shows:
>
> adding new entry CN=Joe Blow, ou=internal, ou=people, o=Tivoli Systems
>
> and ends with:
>
> ldap_add: Object class violation
>
> I've checked my schema. I'm requiring objectclass, sn, cn and uid
> and all are
> present.
>
> The objectclass is tivoliPerson which is based on organizationalPerson.
>
>
>