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

Re: naming attribute 'cn' not present in entry (64)



--On Wednesday, October 24, 2007 5:21 PM +0800 Benny Chee <chee.benny@gmail.com> wrote:

Hi all,

  I ve been trying to add an new custom objectclass
(ndsLoginProperties) and i m always getting this error. Anyone can
decipher it?

Oct 24 17:12:31 ldap slapd[79408]: bdb_referrals: op=104
target="cn=NDS,ou=Policies,dc=example,dc=com"
matched="ou=Policies,dc=example,dc=com"
Oct 24 17:12:31 ldap slapd[79408]: ==> bdb_add:
cn=NDS,ou=Policies,dc=example,dc=com
Oct 24 17:12:31 ldap slapd[79408]: daemon: select: listen=6
active_threads=0 tvp=NULL
Oct 24 17:12:31 ldap slapd[79408]: bdb_add: entry failed schema check:
naming attribute 'cn' is not present in entry (64)
Oct 24 17:12:31 ldap slapd[79408]: daemon: select: listen=7
active_threads=0 tvp=NULL
Oct 24 17:12:31 ldap slapd[79408]: send_ldap_result: conn=14 op=1 p=3
Oct 24 17:12:31 ldap slapd[79408]: send_ldap_result: err=64 matched=""
text="naming attribute 'cn' is not present in entry"
Oct 24 17:12:31 ldap slapd[79408]: send_ldap_response: msgid=2 tag=105
err=64 Oct 24 17:12:31 ldap slapd[79408]: conn=14 op=1 RESULT tag=105
err=64 text=naming attribute 'cn' is not present in entry

It is pretty simple. You don't have a value of cn: NDS in your LDIF file. So just like it says, you are missing the naming attribute cn with a value of NDS in the entry.


--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration