| Previous | Next |
| RPC_S_PRF_ELT_NOT_REMOVED | RPC_S_GRP_ELT_NOT_REMOVED |
RPC_S_GRP_ELT_NOT_ADDED
A member was not added to the RPC name-service group.
RPC_S_GRP_ELT_NOT_ADDED is RPC status 1928 (0x788). RPC groups are name-service entries containing member entry names; they are used to organize discovery names, not Windows security groups. The code means RpcNsGroupMbrAdd could not persist the requested member.
Conditions that prevent the add
- the group entry path refers to a server or profile entry rather than an RPC group
- the group or member name syntax is unsupported, inconsistent, or resolves to the wrong namespace
- the caller lacks permission to create the group or modify its membership
- the member is already present and the provisioning path treats duplicate state as a failure
- the backing name service is unavailable, read-only, or undergoing concurrent modification
What to log
Capture canonical group and member names, their syntax values, whether the group existed, its observed entry type, caller identity, provider, deployment transaction, and the returned RPC code. Enumerate group membership after failure. A member entry need not be a live endpoint at the moment of addition, so keep namespace modification evidence separate from connectivity tests.
Diagnostic steps
Inspect the target entry and enumerate current group members. Verify that the member is not already present under another canonical spelling and that the group is not an incompatible entry type. Test creation of a disposable group in the same parent to isolate permission or provider failures.
Review concurrent provisioning and rollback activity. If multiple controllers own membership, define one reconciliation authority or use serialized changes; blind add/remove loops can oscillate and produce misleading transient failures.
Recovery strategy
Repair the entry type, name syntax, provider, or access control and then add the member idempotently. If a matching member already exists, verify it and continue. Never replace an existing server/profile entry with a group merely because the desired name collided.
Applications should distinguish name-service publication from endpoint registration and health. Report readiness only after the intended membership can be read back, while preserving other group members managed by separate deployments.
Difference from profile membership
An RPC group is a list of entry names. An RPC profile element additionally carries interface and version selection plus priority. RPC_S_PRF_ELT_NOT_ADDED therefore requires different identity fields and diagnostics.
Example
A failover installer tries to add a regional service entry to a shared RPC group, but the path was previously created as a profile. The add returns 1928. Moving the group to a dedicated name and preserving the existing profile avoids destructive conversion.
References
- Microsoft: System Error Codes (1700–3999)
- Microsoft: Win32 Error Codes in MS-ERREF
- Microsoft: RPC return values
- Microsoft: RpcNsGroupMbrAdd
- Microsoft: The RPC name service database
Looking for a different code? Search another status or error code.