Trace showed -601 error on renamed object

DSMaint procedure had recently been run on one of the 4.10 servers
Trace showed -601 error on renamed object
Error: 251 -251 FFFFFF05 = DSERR_NO_SUCH_PROPERTY
Error: 251 -251 FFFFFF05 = DSERR_MESSAGE_QUEUE_FULL
Error: 251 -251 FFFFFF05 = DSERR_UNKNOWN_REQUEST
Error: 601 -601 0xFFFFFDA7 = ERR_NO_SUCH_ENTRY
Report Synchronization status shows all servers reporting one server getting the -251.
Master sees new server as 0_0 (or a renamed object)

Remove DS off of one of the conflicting servers, thus eliminating the server from the ring. 1)  First manually remove the replicas off of the server that is reporting the -251. (Via the -xk2, -xk3 procedure). See TID #7001592 - Manually Removing All Replicas From a Server; DSREPAIR -XK2 for more information on this procedure. 2)  Manually clean up the replica ring using DSREPAIR -A.  This should clean out the -251s and the -601s (if the renamed object exists on the server that is being removed from the replica ring.)   3)  Try adding a replica back on to the server. If at this point you are still getting -251 errors adding a replica, then the server object itself is corrupted.  This necessitates removing DS from the server.  See this TID #10013746 - Forcing NDS off a server for more information on removing DS. 4)  Once DS is successfully removed, then install DS again on the server and add the replicas. This should proceed without problem.

The causes of these particular errors are varied, but in one situation, seemed to be a direct result of having two servers in the tree with the same server name and IPX.  Fortunately, only one server was impacted. In this case, when two servers are on the tree at the same time, the other servers will try to sync with them- either to one or to both.  This results in two different responses being returned.  Each server has a list of all the other servers in the tree in its remote server ID list. When there are two servers return DS information to the server that is requesting is, then that server may see two objects with the same name- in this case a server object- and one of the objects gets renamed.  In this case, the customer was extremely fortunate that there were no other servers or objects that were renamed. Corruption was limited.
Formerly known as TID# 10016966