What does Windows error code 1929 (RPC_S_GRP_ELT_NOT_REMOVED) mean?

 
Previous Next
RPC_S_GRP_ELT_NOT_ADDED ERROR_KM_DRIVER_BLOCKED

RPC_S_GRP_ELT_NOT_REMOVED

The RPC group member could not be removed.

RPC_S_GRP_ELT_NOT_REMOVED is RPC status 1929 (0x789). The operation targets one member name inside an RPC name-service group. It can fail even though the group remains readable and other members are valid, so cleanup must inspect group state rather than deleting the group wholesale.

Why removal fails

  • the supplied member name or syntax does not match the canonical value stored in the group
  • the target entry is not an RPC group or was replaced during a namespace migration
  • the caller can enumerate membership but lacks modification rights
  • another process already removed the member or concurrently changed the group
  • the name-service provider cannot complete the write because it is unavailable or read-only

Evidence for a safe cleanup decision

Log the group path, requested member path, both name syntaxes, existing entry type, current member list hash or count, caller identity, deployment owner, and provider result. Re-enumerate after receiving 1929. A missing member usually means desired cleanup is already achieved, whereas a similarly named member may belong to another installation.

Investigation order

Use group inquiry functions to obtain the exact stored member names. Compare canonical values, not display labels. Verify that cleanup uses the same namespace root and syntax as provisioning, especially when defaults can be changed through RPC name-service configuration.

Check permissions and concurrent automation. If the member remains, determine who owns it before forcing removal. If it disappeared, make the uninstaller idempotent rather than converting an already-complete state into a persistent error.

Recovery and prevention

Correct identity fields or permissions, restore provider health, and remove only the confirmed member. Delete the group only when it is empty and owned exclusively by the retiring component.

Persist canonical member names at installation time and attach deployment ownership in an external inventory. Reconciliation should tolerate a missing member, detect conflicting ownership, and avoid removing entries merely because a host is temporarily offline.

Difference from a missing group member result

RPC_S_GROUP_MEMBER_NOT_FOUND directly reports that a requested member cannot be found during lookup. Status 1929 reports failure of the removal operation; the member may still exist, may already be gone, or may not have matched the supplied identity.

Example

A rollback passes a DNS-style member name while the group stores the same server under a different RPC name syntax. Removal returns 1929. Enumerating and using the stored canonical member removes the correct entry without affecting other members.

References

Looking for a different code? Search another status or error code.