Source: eDirectory or NDS
Explanation: An attempt was made to create a replica on a server that already has
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 was made to transition a new replica on the source server to a replica state of On while the replica state of one of the child partitions is still in a new replica state.
Action: Before setting a new replica to a replica state of On when creating an eDirectory or NDS partition, create and turn On a subordinate reference for each of the child partitions.
Possible Cause: An attempt was made to send schema updates to the target server while the target server's schema is locked due to a new schema epoch. A server that is receiving a new schema epoch cannot receive schema updates until the epoch has completed.
Action: Before sending schema updates to a server, make sure the schema is not is the process of being updated. If this error keeps occurring in this instance, handle this error as a schema synchronization issue.
Possible Cause: A request was received to begin replica synchronization with the specified server while the specified eDirectory or NDS partition on the target server was being synchronized by the replica synchronization background process.
Action: If this error keeps occurring in this instance, handle this error as a partition operation issue.
Wait. This is a normal error immediately after a partition operation has been initiated.
If this error persists, check to see whether this error indicates that the target server does not recognize a replica of the partition on the source server.
Confirm this through the dsrepair.log, or by watching DSTRACE.
If the partition remains busy for more than a few hours, abort the partition operation on the source server.
You can also remove the source server from the tree, or contact a Novell Support Provider.