Error -625 reported by one server to all other servers in the tree

  • 7000640
  • 10-Jun-2008
  • 26-Apr-2012

Environment

Products:
Novell Directory Services
Novell eDirectory

Situation

Symptoms:
One server repors error -625 to all other servers in the tree
Multiple sets of NDS objects including NCP server objects with the same name for the same physical servers in different contexts of the tree
Duplicate sets of NDS objects including NCP server objects with the same name for the same physical servers in different contexts of the tree
Multiple NCP server objects for the same phyiscal server in different contexts with the same IP Address
Duplicate NCP server objects for the same phyiscal server in different contexts with the same IP Address
ERROR: "Server is up and running" while trying to remove additional NCP server object of the same server

Resolution


Method A:
  1. Down the server, remove the additional set of NDS objects including NCP server objects and bring up the server
  2. If error -625 persists, restore .NDO, .$DU, DSBK Backup, embox backup or backup taken using third-party backup softwares if any. Disable schema sync and replica sync. Run dsrepair command and make sure server context and tree name are correct.
  3. -XK2 the server. Please refer the following TID to perform a -XK2 to manually remove all replicas from a server. See tid 7001952
  4. Add the required replicas back on the server
Method B:
  1. Down the server, remove the additional set of NDS objects including NCP server objects and bring up the server
  2. If dsrepair shows wrong server name and context, dsdump may be need to be used to fix the Pseudo Server issue. Please contact Novell Technical Services if dsdump needs to be used. Run dsrepair command and make sure server context and tree name are correct
  3. -XK2 the server. Please refer the following TID to perform a -XK2 to manually remove all replicas from a server.
    https://support.novell.com/docs/Tids/Solutions/10026822.html
  4. Add the required replicas back on the server
Method C:
  1. Down the server, remove the additional set of NDS objects including NCP server objects and bring up the server. Run dsrepair command and make sure server context and tree name are correct
  2. If error -625 persists, take the trustee backup if required
  3. Remove DS, remove all associated objects of the server if any, clean the replica rings, reinstall DS, add required replicas back on the server, restore the trustees if required