[
https://issues.apache.org/jira/browse/DIRSERVER-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689279#comment-13689279
]
Emmanuel Lecharny commented on DIRSERVER-1647:
----------------------------------------------
Modifyng the schema is *not*supported. Not yet.
The only possible way is to delete the schema element, and to add the new one.
The workaround is to edit the LDIF file the way you did.
Is it convenient ? No, certainly not. Will it be fixed ? Yes. When ? Sadly,
when we will have time...
> Unable to enable/modify/delete schema
> -------------------------------------
>
> Key: DIRSERVER-1647
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1647
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: schema
> Affects Versions: 2.0.0-M2
> Reporter: Aaron J Angel
> Fix For: 2.0.0-RC1
>
>
> Attempting to edit, enable, or delete a disabled schema fails with the
> following:
> Error while executing LDIF
> - [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for MessageType :
> MODIFY_REQUES
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
> UNWILLING_TO_PERFORM: failed for MessageType : MODIFY_REQUEST
> Message ID : 22
> Modify Request
> Object : 'cn=nis,ou=schema'
> Modification[0]
> Operation : replace
> Modification
> m-disabled: FALSE
> org.apache.directory.shared.ldap.model.message.ModifyRequestImpl@b9bf625a:
> ERR_11001 Cannot load the unknown schema nis]; remaining name
> 'cn=nis,ou=schema'
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3105)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2978)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2785)
> at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1468)
> at
> com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:273)
> at
> com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:190)
> at
> org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper$2.run(JNDIConnectionWrapper.java:454)
> 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.modifyEntry(JNDIConnectionWrapper.java:502)
> at
> org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifJob.importLdifRecord(ImportLdifJob.java:507)
> at
> org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifJob.importLdif(ImportLdifJob.java:267)
> at
> org.apache.directory.studio.ldapbrowser.core.jobs.ExecuteLdifRunnable.run(ExecuteLdifRunnable.java:143)
> at
> org.apache.directory.studio.ldapbrowser.core.jobs.UpdateEntryRunnable.run(UpdateEntryRunnable.java:58)
> at
> org.apache.directory.studio.connection.ui.RunnableContextRunner$1.run(RunnableContextRunner.java:113)
> at
> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for MessageType :
> MODIFY_REQUEST
> Message ID : 22
> Modify Request
> Object : 'cn=nis,ou=schema'
> Modification[0]
> Operation : replace
> Modification
> m-disabled: FALSE
> org.apache.directory.shared.ldap.model.message.ModifyRequestImpl@b9bf625a:
> ERR_11001 Cannot load the unknown schema nis]
> Upon installation, the nis schema was enabled by removing the m-disabled
> attribute from the entry. Upon discovering that posixGroup was STRUCTURAL, I
> disabled the nis schema. Now, when trying to modify the objectClass entry
> for posixGroup, or even when attempting to delete the nis schema entirely to
> start over, the above error message is presented in Directory Studio.
> For my application, I need to edit or replace the default nis schema with one
> compatible with rfc2307bis (e.g., posixGroup must be AUXILIARY, not
> STRUCTURAL).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
