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

Re: Fw: ldapadd is failing - error: Naming violation additional info: value of naming attribute 'ou'is not present in entry

To: Raed Nashef <rnashef@baxglobal.com>
Subject: Re: Fw: ldapadd is failing - error: Naming violation additional info: value of naming attribute 'ou'is not present in entry
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Date: Sat, 17 Jan 2004 04:51:40 +0100
Cc: openldap-software@OpenLDAP.org
In-reply-to: <OF8E27E593.968E26E7-ON88256E1E.00136ED5-88256E1E.0013B6DC@baxglobal.com>
References: <OF8E27E593.968E26E7-ON88256E1E.00136ED5-88256E1E.0013B6DC@baxglobal.com>

Raed Nashef writes:
> I added another ou for "IT Services" as shown below, and that works.
> It is interesting why it worked with 2.0.23 and does not work with
> this new version !!!

'Interesting!!!'?  It was a bug in 2.0.23 that it worked.  That bug has
now been fixed, and it returns an error like the LDAP spec says it
should.

-- 
Hallvard

Follow-Ups:
- RE: Fw: ldapadd is failing - error: Naming violation additional info: value of naming attribute 'ou'is not present in entry
  - From: "Howard Chu" <hyc@highlandsun.com>

References:
- Fw: ldapadd is failing - error: Naming violation additional info: value of naming attribute 'ou'is not present in entry
  - From: Raed Nashef <rnashef@baxglobal.com>

Prev by Date: Fw: ldapadd is failing - error: Naming violation additional info: value of naming attribute 'ou'is not present in entry
Next by Date: Re: RedHat 7.0 install problem: configure fails with "BerkeleyDB version incompatible": now what?
Index(es):
- Chronological
- Thread