[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: ldapmodify returns "No such object (32)" for user besides ROO TDN
Good day,
I would have replied to your original message, but I couldn't find it in my
inbox.
"No such object" will get returned if your ACLs are incorrect. I know you
said you thought they were right, but it would help if you posted all of
them.
Running slapd with some debugging turned on would help as well. (slapd -d 1)
============================
Darren Gamble
Planner, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
(403) 781-4948
> -----Original Message-----
> From: John Ziniti [mailto:jziniti@speakeasy.org]
> Sent: Friday, August 23, 2002 6:37 AM
> To: Pierangelo Masarati
> Cc: openldap-software@OpenLDAP.org
> Subject: Re: ldapmodify returns "No such object (32)" for user besides
> ROOTDN
>
>
> > It means the PARENT does not exist. Looks like you're
> > trying to add an entry BEFORE adding the entry corresponding
> > to the suffix of your database.
>
> I thought that at first, but the PARENT is without
> a doubt in the database. Evidence:
>
> $ ldapmodify -D <ROOTDN> -f modifications.ldif
> $ ldapmodify -D <OTHERDN> -f modifications.ldif
>
> The first succeeds and the second fails with "No such object".
>
>
>