XADM: Lightweight Directory Access Protocol Must Be Used to Delete Routing Groups (264441)

SYMPTOMS

When a server is displayed as a member of two Routing Groups (RGs), if you try to consolidate the member server by moving the member server to a single RG, the user interface (UI) may prevent you from doing so.

The following procedures generate the following results:

• A drag-and-drop operation to move the duplicate member server from the second RG to a third RG does not resolve the problem, but you do not receive any error messages.
• A drag-and-drop operation to move the duplicate member server from the third RG to the second RG does not resolve the problem, but you do not receive any error messages.
• A drag-and-drop operation to move the duplicate member server from separate servers to the first RG does not resolve the problem, and you receive an ambiguous error message that is similar to the following:
  ID no. 8000ffff

Routing does not work properly between the two RGs.

After replication takes place, the following conditions exist:

• The original master server is in the first RG.
• Two servers are in the second RG (one master, one member).
• One server is in the third RG. That server is displayed in the UI as a member, not a master, even though Lightweight Directory Access Protocol (LDAP) displays the server as a master.

The same server is displayed in both RGs.