Re[2]: no validator for syntax

[Mark_Symmonds@consultec-inc.com]

>From core.schema:

     objectclass ( 2.5.6.12 NAME 'applicationEntity' SUP top STRUCTURAL
             MUST ( presentationAddress $ cn )
             MAY ( supportedApplicationContext $ seeAlso $ ou $ o $ l $
             description ) )

     objectclass ( 2.5.6.13 NAME 'dSA' SUP applicationEntity STRUCTURAL
             MAY knowledgeInformation )

     ____________________Reply Separator____________________
     Subject:  Re: no validator for syntax
     Author:   owner-openldap-software@OpenLDAP.org
     Date:          5/9/2001 3:29 PM




I don't think core.schema has an applicationEntity objectclass.


----- Original Message -----
From: <Mark_Symmonds@consultec-inc.com>
To: <openldap-software@OpenLDAP.org>
Sent: Wednesday, May 09, 2001 3:12 PM
Subject: no validator for syntax


> Hello,
>
> Our development group is having a problem with getting an ldif in with
> ldapadd, and I do not know enough of the syntax of LDAP to help them so I
> was wondering if someone here could help.  Here are the entries we are
> adding in the ldif:
>
> dn: c=us
> objectclass: top
> objectclass: country
> c: us
>
> dn: o=Company, c=us
> objectclass: top
> objectclass: organization
> o: Company
>
> dn: ou=Applications,o=Company, c=us
> objectclass: organizationalUnit
> objectclass: top
> ou: Applications
>
> dn: cn=MEVS-FL,ou=Applications,o=Company,c=us
> objectclass: top
> objectclass: applicationEntity
> presentationAddress: /florida
> cn: MEVS-FL
>
> When I ldapadd the first three entries went in fine; however the fourth
> entry results in the following error:
>
> # ./ldapadd -x -f tim.ldif -D "cn=Manager, c=us" -W
> adding new entry "cn=MEVS-FL,ou=Applications,o=Company, c=us"
> ldap_add: Invalid syntax
>         additional info: no validator for syntax
>
> ldif_record() = 21
>
> We are using the core.schema and OpenLDAP 2.0.7.  Any help would be
greatly
> appreciated.
>
> Mark Symmonds
>
>