Source: eDirectory or NDS
Explanation: The time synchronization used by eDirectory or NDS is not synchronized between the source and target servers.
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: An attempt to modify an object through the eDirectory or NDS background processes failed because the modification timestamp of the attribute value on the target server was higher than the modification timestamp of the attribute value on the source server.
Action: Additional information regarding the objects and attributes involved can be obtained by using DSTRACE on the target server with the Collisions flag set.
Possible Cause: Occurrence of this error during a Change Replica Type partition operation indicates the eDirectory or NDS server targeted to become the new master replica has modification timestamps in its replica that are higher than its current time provided by Time Synchronization.
If you are using DSTRACE on the eDirectory or NDS server targeted to become the new master and the Synchronization or Partition Operation flags are set, the following message is displayed:
*CNTL: SetNewMaster for [PartitionRootObjectEntryID] <PartitionRootObjectName>, old highest is Timestamp, current time is CurrentTime, ERR_TIME_NOT_SYNCHRONIZED
Action: Compare the time difference between Timestamp and CurrentTime on the server. You can determine the amount of time that must pass before the operation will process.
Warning: If the master copy was corrupt in any way, that corruption will be dispersed to the other replicas when a Repair Time Stamps or Receive Updates action is performed. Repair Time Stamps and Receive Updates can also cause considerable traffic on the network. You might have to do this one partition at a time.
If the time difference is significant, attempt to abort the partition operation and resolve the issue using Repair Time Stamps.