| Previous | Next |
| STATUS_DRIVER_CANCEL_TIMEOUT | STATUS_MAPPED_ALIGNMENT |
STATUS_REPLY_MESSAGE_MISMATCH
The reply targets the wrong outstanding LPC request
Synchronous LPC request/reply processing associates a reply with a specific waiting client context. A stale client ID, reused message header, reply sent through the wrong connection, or two workers replying to one request can break that association and produce this status.
The failure often exposes a server-side ownership bug. Once a worker accepts a request, exactly one path should own the right to reply or abandon it. Copying native message headers into a long-lived queue without preserving the required identifiers can also make a later reply refer to an obsolete wait.
What to inspect
- Log request message ID, client ID, connection identity, receiving worker, and replying worker.
- Ensure timeout and cancellation paths atomically revoke the right to send a normal reply.
- Do not synthesize or reuse native reply headers from an earlier request.
- Check for duplicate dispatch caused by both queue and completion-list consumers processing one message.
References
- Microsoft Open Specifications: NTSTATUS values
- System Informer PHNT: native LPC definitions
- ReactOS source: LPC implementation
- Wine source: server-side request and reply handling
Looking for a different code? Search another status or error code.