| 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. AllStat describes it as “The message filter rejected the call.” In the COM/RPC call control, message filtering, apartment routing, marshaling, security negotiation, or remote object lifetime, the code identifies a specific failure boundary and should not be replaced by a generic COM exception.
Handling this result correctly requires the code-specific postcondition, not merely the fact that FAILED(hr) is true.
Where it is encountered
- Cross-apartment or cross-process COM method invocation and activation. Record the interface, method, component version, thread, apartment, process, and correlation ID.
- 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 for it is a COM call that the server or message filter refuses instead of accepting or asking for a later retry. Keep it attached to that operation; the same numeric severity outside the owning API does not supply enough context.
Decisive interpretation boundary
Before choosing recovery, verify that the rejection is correlated with server state and the caller knows whether a new user action or state transition is required. That boundary prevents it from being misclassified as corruption, network failure, or a reason for an unsafe automatic retry.
Also confirm that all observed objects, tokens, buffers, proxies, metadata files, or ACLs belong to the current operation generation and were not retained from an earlier attempt.
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 for it can duplicate effects, deepen reentrancy, or hide an invalid lifetime transition.
Lifetime, retry, and cleanup rules
After it, determine whether the current object, interface pointer, call context, token, stream, metadata reader, asynchronous operation, or access-control instance remains valid. Release only resources owned by the failing attempt, cancel callbacks through their documented mechanism, and avoid double close, double commit, repeated activation, or replay of a non-idempotent remote method.
The retry policy for it should state the trigger, maximum attempts, cancellation owner, and reconciliation step for effects that may have completed elsewhere.
Difference from nearby HRESULTs
It is a refusal; RPC_E_SERVERCALL_RETRYLATER explicitly invites a delayed retry.
The distinction around it should be represented explicitly in control flow and operational dashboards.
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.
A regression test should reproduce it, assert the raw HRESULT and all relevant outputs, then correct only the decisive condition and verify the intended success or neighboring failure result.
References
- Microsoft: COM RPC error codes
- Microsoft: IMessageFilter
- Microsoft: RetryRejectedCall
- Microsoft: CoInitialize
- Microsoft: CoInitializeSecurity
- Microsoft: marshaling rules
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.