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

Re: new schema error 19

Hi Michael,

LDAP Error Code 19:
0x13
19
LDAP_CONSTRAINT_VIOLATION: Indicates that the attribute value specified in a modify, add, or modify DN operation violates constraints placed on the attribute. The constraint can be one of size or content (string only, no binary).



Full list of LDAP error codes:
http://www.directory-info.com/LDAP/LDAPErrorCodes.html

Make sure that you also have "cn" and "description" attributes defined in your schema.

Regards,
Shuh

----- Original Message ----- From: "Michael Oliver" <ollie@alariussystems.com>
To: "'OpenLDAP software list'" <openldap-software@OpenLDAP.org>
Sent: Thursday, February 23, 2006 1:54 PM
Subject: new schema error 19


I am trying to write our own schema for OpenLDAP and I have applied for a
new IANA base number but derived a number that didn't appear to conflict
with any of the schemas in the distribution.



First I created to attribute types



attributetype ( 1.3.6.1.4.1.1.1961 NAME 'propertyName'

     DESC 'Java Properties object attribute for Property Name'

     EQUALITY caseIgnoreMatch

     SUBSTR caseIgnoreSubstringsMatch

     SYNTAX 1.3.6.1.4.1.1466.115.121.1.15

     SINGLE-VALUE )



attributetype ( 1.3.6.1.4.1.1.1962 NAME 'propertyValue'

     DESC 'Java Properties object attribute for Property Value'

     EQUALITY caseIgnoreMatch

     SUBSTR caseIgnoreSubstringsMatch

     SYNTAX 1.3.6.1.4.1.1466.115.121.1.15

     SINGLE-VALUE )



And added the alarius.schema to the slapd.conf and it started fine and the
attributeTypes showed in my JXplorer.cool.



So then I wanted an objectClass to add these attributeType to.



objectclass ( 1.3.6.1.4.1.2.1964 NAME 'javaProperty'

     DESC 'Persist Java Property name and value'

     SUP top STRUCTURAL

     MUST ( cn $ propertyName $ propertyValue )

     MAY ( description ) )



But when I restart after that, the service fails to start and reports "error
code 19" as the cause.



I tried to find error 19 to no avail.



I compared that objectclass definition to the objectclass for 'person' and
other than the different attributes, it looks the same to me. So what am I
missing.



Ollie










--Boundary_(ID_tfLcqRgYRlrvqjFlvDPEhg)--