Directory ApacheDS
  1. Directory ApacheDS
  2. DIRSERVER-1697

Creation of new syntax fails due to ERR_277 Attribute m-obsolete not declared in objectClasses of entry

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 1.5.7
    • Fix Version/s: 2.0.0-M7
    • Component/s: schema
    • Labels:
      None
    • Environment:
      Windows 7 x64, ApacheDS 1.5.7, Apache Directory Studio 1.5.3.v20100330

      Description

      This error is encountered when trying to import my ldif containing new syntax definitions:

      Error while importing LDIF

      • [LDAP: error code 65 - OBJECT_CLASS_VIOLATION: failed for Add Request
        javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - OBJECT_CLASS_VIOLATION: failed for Add Request :
        ClientEntry
        dn: m-oid=1.3.6.1.4.1.115.1.2.20.1.1,ou=syntaxes,cn=system,ou=schema
        objectClass: metaSyntax
        objectClass: metaTop
        objectClass: top
        x-enum: America/New_York
        x-enum: America/Detroit
        x-enum: America/Kentucky/Louisville
        x-humanreadable: TRUE
        m-oid: 1.3.6.1.4.1.115.1.2.20.1.1
        m-obsolete: FALSE
        m-description: A list of allowable time zones
        : ERR_277 Attribute m-obsolete not declared in objectClasses of entry m-oid=1.3.6.1.4.1.115.1.2.20.1.1,ou=syntaxes,cn=system,ou=schema]; remaining name 'm-oid=1.3.6.1.4.1.115.1.2.20.1.1,ou=syntaxes,cn=system,ou=schema'
        at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3098)
        at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3013)
        at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2820)
        at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:791)
        at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
        at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
        at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper$4.run(JNDIConnectionWrapper.java:658)
        at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.runAndMonitor(JNDIConnectionWrapper.java:1272)
        at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.checkConnectionAndRunAndMonitor(JNDIConnectionWrapper.java:1203)
        at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.createEntry(JNDIConnectionWrapper.java:704)
        at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifJob.importLdifRecord(ImportLdifJob.java:457)
        at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifJob.importLdif(ImportLdifJob.java:267)
        at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifJob.executeNotificationJob(ImportLdifJob.java:204)
        at org.apache.directory.studio.ldapbrowser.core.jobs.AbstractNotificationJob.executeAsyncJob(AbstractNotificationJob.java:43)
        at org.apache.directory.studio.ldapbrowser.core.jobs.AbstractEclipseJob.run(AbstractEclipseJob.java:101)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

      [LDAP: error code 65 - OBJECT_CLASS_VIOLATION: failed for Add Request :
      ClientEntry
      dn: m-oid=1.3.6.1.4.1.115.1.2.20.1.1,ou=syntaxes,cn=system,ou=schema
      objectClass: metaSyntax
      objectClass: metaTop
      objectClass: top
      x-enum: America/New_York
      x-enum: America/Detroit
      x-enum: America/Kentucky/Louisville
      x-humanreadable: TRUE
      m-oid: 1.3.6.1.4.1.115.1.2.20.1.1
      m-obsolete: FALSE
      m-description: A list of allowable time zones
      : ERR_277 Attribute m-obsolete not declared in objectClasses of entry m-oid=1.3.6.1.4.1.115.1.2.20.1.1,ou=syntaxes,cn=system,ou=schema]

      1. time_zone_schema.ldif
        1 kB
        lucas theisen
      2. EnumSyntaxChecker.java
        1 kB
        lucas theisen

        Activity

        Hide
        Emmanuel Lecharny added a comment -

        It should be fixed in 2.0.0. The MetaSyntax ovjectClass contains the m-obsolete AT in its m-may list :

        version: 1
        dn: m-oid=1.3.6.1.4.1.18060.0.4.0.3.4,ou=objectClasses,cn=apachemeta,ou=schema
        m-oid: 1.3.6.1.4.1.18060.0.4.0.3.4
        m-name: metaSyntax
        m-description: meta definition of the Syntax object
        objectclass: top
        objectclass: metaTop
        objectclass: metaObjectClass
        m-obsolete: FALSE
        m-supobjectclass: metaTop
        m-typeobjectclass: STRUCTURAL
        m-may: x-not-human-readable
        m-may: m-obsolete
        creatorsname: uid=admin,ou=system

        Show
        Emmanuel Lecharny added a comment - It should be fixed in 2.0.0. The MetaSyntax ovjectClass contains the m-obsolete AT in its m-may list : version: 1 dn: m-oid=1.3.6.1.4.1.18060.0.4.0.3.4,ou=objectClasses,cn=apachemeta,ou=schema m-oid: 1.3.6.1.4.1.18060.0.4.0.3.4 m-name: metaSyntax m-description: meta definition of the Syntax object objectclass: top objectclass: metaTop objectclass: metaObjectClass m-obsolete: FALSE m-supobjectclass: metaTop m-typeobjectclass: STRUCTURAL m-may: x-not-human-readable m-may: m-obsolete creatorsname: uid=admin,ou=system
        Hide
        lucas theisen added a comment -

        Attaching the ldif, and the EnumSyntaxChecker refered to in the ldif.

        Show
        lucas theisen added a comment - Attaching the ldif, and the EnumSyntaxChecker refered to in the ldif.

          People

          • Assignee:
            Unassigned
            Reporter:
            lucas theisen
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development