[Date Prev][Date Next]
RE: Asserion Failed when entry data using ldif
Thank you for reply,
i understand if char # in ldif treated as comment, but
i din't realiZe if it affect to entryCSN attribute.
because most of the entry of my ldap has char # in
their entryCSN and i did not find problem (still can
insert them into ldap).
But why taht entry that cause stop inserting into my
what is the exact format for entryCSN should be?
Thank you for your kindness for replying my question
--- "Tay, Gary" <Gary_Tay@platts.com> wrote:
> No sure if the # chars in yr ldif files (entryCSN)
> are interpreted as
> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org] On
> Behalf Of Logan Romanov
> Sent: Tuesday, September 21, 2004 10:06 AM
> To: openldap-software@OpenLDAP.org
> Subject: Asserion Failed when entry data using ldif
> i was trying to add an ldif file into my ldap
> when the insertion is running,suddenly it stopped,
> produce this message:
> "slapadd: schema_init.c:1793: Uidvalidity: Assertion
> `0' failed"
> it stopped in this part or my ldif
> -----part of my ldif--------------------
> dn: ou=aaaa,dc=bbb,dc=com
> creatorsName: cn=manager,dc=bbb,dc=com
> createTimestamp: 20040713042205Z
> modifiersName: cn=manager,dc=bbb,dc=com
> modifyTimestamp: 20040713042205Z
> objectClass: organizationalUnit
> ou: aaaa
> structuralObjectClass: organizationalUnit
> entryCSN: 20040826094121Z#000002#00#000000
> entryUUID:: 1N84hIuPECiNL5da1IqL4Q==
> i have searched google and search in openldap
> list but found nothing that could be used as
> not yet at least.
> Maybe someone could help me with this?
> i really appreciate
> Thank you in advance
> Yahoo! Messenger - all new features - even more fun!
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com