Source: eDirectory or NDS
Explanation: The requested attribute could not be found. In eDirectory or NDS, if an attribute does not contain a value, then the attribute does not exist for the specific object.
The request might be
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: The definition for the specified schema attribute does not exist on the server replying to the request.
Action: Look at what type of object the error is occurring on.
If the object is a simple object, such as a single user that is not a critical user, delete and recreate the problem object.
If it is the source server that is missing the attribute, then 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.
Possible Cause: The specified object does not have the specified attribute.
Action: Perform a Send All Objects to Every Replica in the Ring operation from DSREPAIR.
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.
Possible Cause: The requester does not have sufficient rights to the attributes for the specified object.
Action: If appropriate, assign the requester the necessary rights.