| Previous | Next |
| RPC_NT_NO_MORE_BINDINGS | EPT_NT_CANT_CREATE |
RPC_NT_GROUP_MEMBER_NOT_FOUND
Requested RPC group member was not found
RPC_NT_GROUP_MEMBER_NOT_FOUND belongs to the Windows RPC runtime NTSTATUS facility. For RPC_NT_GROUP_MEMBER_NOT_FOUND, mS-RPCE extends the DCE/RPC model: generated stubs marshal parameters, the runtime binds to an endpoint and protocol sequence, and security or transport failures can be returned as RPC facility status values.
This status belongs to RPC name-service style lookup, not to Windows local group membership. It indicates that the runtime could not find a member entry within the RPC group being queried.
When this appears in modern Windows troubleshooting, first identify whether the application still uses name-service/group APIs or whether the code is translating an older RPC status. Endpoint mapper registration problems usually surface as different statuses.
What to check for RPC_NT_GROUP_MEMBER_NOT_FOUND
- Identify the exact RPC name-service call or compatibility layer returning the status.
- Verify the group name syntax and member UUID being queried.
- Do not diagnose Active Directory group membership unless the application explicitly maps RPC group data to directory objects.
References for RPC_NT_GROUP_MEMBER_NOT_FOUND
- Microsoft Open Specifications: MS-RPCE overview
- The Open Group: DCE 1.1 RPC introduction
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.