OU object not getting deleted - getting (Error-610)Illegal NDS name

Hi,

There is an Organizational Unit object in eDirectory. It does not have any child objects.
I want to delete the object but it is not getting deleted from iManager.
The iManager gives below error:
Error: The Delete Object request failed
(Error-610)Illegal NDS name. Avoid using illegal characters or reduce the number of characters in the object's name.

Another thing is that this object is not shown in Apache LDAP browser OR in iMonitor.

The objects DN length has 241 characters without tree name on it. It has exactly 256 characters with the tree name (T=UTVENV_TREE2)

But from iManager, I am able to modify the attribute and gets updated on this object. But it is not gettting deleted or not getting renamed.
It throws the above error.

Is there anywasy to delete this object?

Please assist.

eDir version: NetIQ eDirectory 9.2.6

Thanks
dk

  • 0  

    If you can find it using iMonitor, then enable advanced options and delete it that way.

    1) enable advanced options (click on top left logo)

    2) find object

    3) click "advanced options", select "Remove Object" ...

    That should do it.

    You should check all replicas to see if the object is gone from them, if not do the same on all servers where it's found.

  • 0 in reply to   

    Hi,

    Thanks for your quick reply.

    I have tried enabling advanced option in iMonitor.

    But when I search that OU object, it throws NDS Error -610. It doesn't show up the object.

    -dk

  • 0

    Have you try to repair with ndsrepair and his Parameters? Do you have a Replikation?

  • 0   in reply to 

    If iMonitor can't find the object (or browse to it), then there might be a database problem, do as suggest.

  • 0 in reply to 

    There was an old eDirectory version. We installed and added a new server to the tree. The old server was removed 6 months ago.

    Now, we have only one server in the tree. But I am not sure when this object was created. It might have been created when the old eDirectory server was in place.

  • 0  

    Did you ever try with iManager Workstation?

    Which kinds of objects reside in the parent container of the OU in question?

  • 0 in reply to   

    The issue was with the OU object, it is a leaf object. It is the only object exists under the parent OU object.

    Yes, I have tried with iManager Workstation and still the same. It is not deleting the OU leaf or Parent object.

    Getting below Error-610 Illegan NDS name message on the iManager workstation log.

    DeleteObjectTask....356 (Error-610)Illegal NDS name. Avoid using illegal characters or reduce the number of characters in the object's name.
    eDirRightsObject....308 (Error-610)Illegal NDS name. Avoid using illegal characters or reduce the number of characters in the object's name.
    eDirRightsObject....233 (Error-610)Illegal NDS name. Avoid using illegal characters or reduce the number of characters in the object's name.
    eDirRightsObject....308 (Error-610)Illegal NDS name. Avoid using illegal characters or reduce the number of characters in the object's name.
    eDirRightsObject....308 (Error-610)Illegal NDS name. Avoid using illegal characters or reduce the number of characters in the object's name.
    eDirRightsObject....308 (Error-610)Illegal NDS name. Avoid using illegal characters or reduce the number of characters in the object's name.
    eDirRightsObject....308 (Error-610)Illegal NDS name. Avoid using illegal characters or reduce the number of characters in the object's name.

    /dk

  • Verified Answer

    +1   in reply to 

    The idea is to (temporarily) reduce the length of a parent container, e.g. from "Marketing" to "MKT". As renaming a container can have serious ramifications (depending on the objectclasses residing underneath) i asked which kinds of objects reside as siblings of the OU in question.

  • 0 in reply to   

    I renamed & reduced the length of the parent OU and immediately after that the child object was shown in the ldap browser.

    And after that I was able to delete the problematic leaf OU object.

    Your suggestion worked.

    Thanks and apprciating your help.