| Previous | Next |
| RPC_S_PROCNUM_OUT_OF_RANGE | RPC_S_UNKNOWN_AUTHN_SERVICE |
RPC_S_BINDING_HAS_NO_AUTH
RPC_S_BINDING_HAS_NO_AUTH means that the RPC binding handle has no authentication information. A client is not required to configure authentication for every binding, but an operation that requires it cannot use an unauthenticated binding.
Inspect the binding with RPC inquiry APIs or the client configuration and confirm which authentication service, level, and identity the server operation requires. Attach authentication to the binding before the protected call rather than assuming transport connectivity implies RPC security.
What to check
- Call
RpcBindingSetAuthInfoon the binding before invoking a procedure that requires authenticated RPC. - Confirm the server accepts the selected authentication service and level.
- Do not treat transport reachability as authentication; a successful connection can still be rejected because the binding has no credentials.
Looking for a different code? Search another status or error code.