| Previous | Next |
| STATUS_NO_GUID_TRANSLATION | STATUS_IMAGE_ALREADY_LOADED |
STATUS_CANNOT_IMPERSONATE
The server cannot impersonate the named-pipe client yet
These statuses belong to the Windows named-pipe path. For STATUS_CANNOT_IMPERSONATE, A named pipe can have multiple instances with the same name, but each instance has its own state, buffer, handles, type mode, read mode, and wait mode.
Named-pipe impersonation uses the security context of the last message read from the client. If the server has not read a client message on that pipe, there is no client token context for the pipe file system to apply.
For STATUS_CANNOT_IMPERSONATE, for diagnostics, record the pipe name, server/client end, instance count, blocking versus nonblocking mode, byte versus message mode, overlapped operation state, and whether the handle is connected, listening, closing, or disconnected.
What to inspect
- Read a client request before calling ImpersonateNamedPipeClient.
- Confirm the handle is the server end of the pipe.
- Check the client impersonation level if impersonation still fails after a read.
References for STATUS_CANNOT_IMPERSONATE
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: ImpersonateNamedPipeClient
- Microsoft: Named Pipes
Looking for a different code? Search another status or error code.