V Po, 26. 04. 2004 v 13:12, Tony Earnshaw pÃÅe:
> man, 26.04.2004 kl. 09.49 skrev David Kmoch:
>
> > Hmm, thats strange, but with GQ-1.0b1 I'm getting the same results
> > - can change anything in the contacts except CN - will produce the same
> > error like Evo.
> >
> > Looks to me like there is problem in Openldap or Evo and GQ share the
> > same bug. Is someone else running Openldap 2.1.22 experiencing this
> > behavior?
>
> Maybe we're talking about 2 different CNs - you about the CN rDN (i.e.
> "bit") in the DN, me about the CN as subsidiary attribute. The CN rDN
> cannot be changed in LDAPv3, the attribute can easily be changed.
My problem is that those two values (CN in DN and CN as subsidiary
attribute) cannot be different. When I try to change CN (as a subsidiary
attribute), I'm getting those error messages. When I update both, it's
fine, but that's possible only with GQ, not with Evo :(
Even tried to modify slapd.conf to
access * by * write
as the only rule just to check the it's not because of badly configured
ACL. But no change :(
GQ
Error modifying entry 'cn=...': Naming violation
Additional error: value of naming attribute 'cn' is not present in entry
SLAPD
entry failed schema check: value of naming attribute 'cn' is not present in entry
David
--
David Kmoch
Technical University of Liberec
Department of Applied Informatics
Halkova 6, 461 17 Liberec
tel: +420 485 353 633
fax: +420 485 353 112
_______________________________________________
evolution maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution
