| Previous | Next |
| RPC_E_SERVERCALL_RETRYLATER | RPC_E_INVALID_CALLDATA |
RPC_E_SERVERCALL_REJECTED
COM server message filter rejected the call
RPC_E_SERVERCALL_REJECTED is HRESULT 2147549451 (0x8001010B) from winerror.h. The documented description is “The message filter rejected the call.” The relevant context is the COM/RPC call control, message filtering, apartment routing, marshaling, security negotiation, or remote object lifetime.
Where it is encountered
- Cross-apartment or cross-process COM method invocation and activation.
- STA message filtering, reentrancy, call cancellation, timeout, or retry handling.
- DCOM security initialization, proxy/stub marshaling, OBJREF processing, and server object lifetime.
The immediate focus is a COM call that the server or message filter refuses instead of accepting or asking for a later retry.
What to verify
Verify that the rejection is correlated with server state and the caller knows whether a new user action or state transition is required. This distinction prevents it from being misclassified as corruption, network failure, or a reason for an unsafe automatic retry.
Correct handling and recovery
Do not automatically replay non-idempotent calls. Surface the rejection, wait for a meaningful state change, or follow the application-specific recovery path.
An unchanged retry loop can duplicate effects, deepen reentrancy, or hide an invalid lifetime transition.
Difference from nearby HRESULTs
It is a refusal; RPC_E_SERVERCALL_RETRYLATER explicitly invites a delayed retry.
Practical scenario
A document server rejects automation while closing a protected document. The client stops retries, refreshes server state, and asks the user to reopen the document.
References
Looking for a different code? Search another status or error code.