Replica stuck in new state - network address problem.

  • 7003120
  • 27-Apr-2009
  • 27-Apr-2012

Environment

Novell eDirectory 8.6 for All Platforms
Novell NetWare 6.0 Support Pack 2
Novell NetWare 5.1 Support Pack 4

Situation

A new NW6 server was introduced into the tree.
Replica Stuck in a NEW state
Error: -654 0xFFFFFD72 = ERR_PARTITION_BUSY.
Error: -603 0xFFFFFDA5 = ERR_NO_SUCH_ATTRIBUTE
A replica was added to one server and another server received it.
A server has a replica in new state, but the server doesn't exist in the replica ring.

Resolution

Change the network address on the new server to be different from any existing servers and reboot the server. DO NOT rename the server while performing this operation. When the server comes back online, run the Limber Process (See TID#:10063122 for the exact procedure).  Run DSRepair -XK2 on both receiving servers to remove all replicas affected  (For detail information on the -XK2 procedure see TID#:7001592).
Run a repair network address in dsrepair on the server receiving the replica and on the server sending the replica. 

Additional Information

Customer accidently configured the internal net address on a new server to be the same as the internal address of an existing server, then he added a replica.
Formerly known as TID# 10075623