| Previous | Next |
| RPC_X_WRONG_PIPE_VERSION | RPC_S_DO_NOT_DISTURB |
RPC_S_COOKIE_AUTH_FAILED
The failure occurred at the RPC HTTP proxy authentication layer
RPC_S_COOKIE_AUTH_FAILED applies to RPC over HTTP and indicates that the proxy rejected cookie-based authentication for the connection. It is separate from RPC interface authentication at the destination server and from ordinary endpoint resolution.
Capture the HTTP proxy endpoint, TLS state, proxy response, cookie source, expiration, scope, and the identity under which the client runs. Check whether an intermediary strips or rewrites cookies and whether the proxy expects integrated authentication instead. Recreating the RPC binding without refreshing invalid proxy credentials normally repeats the failure.
What to inspect
- Separate proxy authentication logs from destination RPC server logs.
- Verify cookie lifetime, audience, path, and secure transport requirements.
- Check load balancer affinity if the proxy uses node-specific session cookies.
References
- Microsoft: using HTTP as an RPC transport
- Microsoft: RPC security layers
- Microsoft: RPC cookie-authentication status
Looking for a different code? Search another status or error code.