| Previous | Next |
| RPC_NT_COOKIE_AUTH_FAILED | RPC_NT_SS_CHAR_TRANS_OPEN_FAIL |
RPC_NT_NO_MORE_ENTRIES
No more RPC auto-handle entries
RPC_NT_NO_MORE_ENTRIES is tied to RPC automatic binding. With an automatic binding handle, generated stub code manages the binding instead of application code selecting a specific server.
This status normally means the auto-handle search has walked through the available server entries and has no more candidates. It should be handled as the end of an enumeration/search path unless the application expected a server name-service database to contain additional exported bindings.
What to check
- Check whether the IDL/ACF uses
[auto_handle]or compiler defaults that select automatic binding. - Verify the server exported binding information into the name-service database expected by the client.
- Handle the status as enumeration exhaustion before retrying the same auto-handle call in a tight loop.
References
- Microsoft RPC: automatic binding handles
- Microsoft RPC: Microsoft binding-handle extensions
- Microsoft RPC: advertising server interfaces
- Microsoft Open Specifications: MS-RPCE overview
Looking for a different code? Search another status or error code.