-633 FFFFFD87 INVALID ENTRY FOR ROOT

Source

eDirectory™

Explanation

An attempt was made to

- Restore an object as the [Root] of the eDirectory tree; however, the object's base class was not Top.
- Assign an object as a partition root object; however, the object's base class was not flagged as a Container in the class's schema class definition.

Warning:

Applying all solutions mentioned in this topic could make the problem worse if the actual cause of the problem is not known. Before following a course of action, make sure that you understand the cause of the error and the consequences for the actions suggested.

Possible Cause

A program fault occurred in the application used to restore or manipulate the object.

Action

Contact the developer of the application.

Possible Cause

If this error occurs during an eDirectory background process, discrepancies might exist between the replicas of a partition.

Action

Perform a database repair on the target server using DSREPAIR.

- If DSREPAIR can resolve the issue and the target server does not hold the master replica of the partition, use DSREPAIR to perform a Receive All Updates from the Master to This Replica operation on the source server.

Warning:

The Receive All Updates from the Master to This Replica operation in DSREPAIR removes the replica and then places the replica back on the server. This operation cannot be performed on the server that holds the master replica. If this operation needs to be performed on the server holding the master replica, reassign the master replica to another replica ring using DSREPAIR before starting this operation.

- If DSREPAIR can resolve the issue and the target server holds the master replica of the partition, use DSREPAIR to perform a Send All Objects to Every Replica in the Ring operation on the target server.

Warning:

When a Send All Objects to Every Replica in the Ring operation is performed on large partitions or partitions with numerous replicas, considerable traffic on the network can result.

- If DSREPAIR cannot resolve the issue, you can remove the replica for the target server using the NDS® Manager, provided the target server does not hold the master replica.

A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For information on trademarks, see Legal Notices.