What does HRESULT 0x80010011 (RPC_E_CANTCALLOUT_AGAIN) mean?

RPC_E_CANTCALLOUT_AGAIN

Second outgoing call is not allowed on the same DDE channel

RPC_E_CANTCALLOUT_AGAIN is HRESULT 2147549201 (0x80010011) from winerror.h. AllStat describes it as “There is no second outgoing call on same channel in DDE conversation.” 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.

Telemetry should preserve RPC_E_CANTCALLOUT_AGAIN as a separate outcome rather than merging it with unrelated COM or WinRT failures.

Decisive interpretation boundary

Before choosing recovery, verify that the active conversation, current outbound call, callback stack, and channel ownership are known. That boundary prevents RPC_E_CANTCALLOUT_AGAIN from being misclassified as corruption, network failure, or a reason for an unsafe automatic retry.

For RPC_E_CANTCALLOUT_AGAIN, 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.

Where it is encountered

• RPC_E_CANTCALLOUT_AGAIN can be returned during cross-apartment or cross-process COM method invocation and activation. For RPC_E_CANTCALLOUT_AGAIN, record the interface, method, component version, thread, apartment, process, and correlation ID.
• RPC_E_CANTCALLOUT_AGAIN can be returned during STA message filtering, reentrancy, call cancellation, timeout, or retry handling. For RPC_E_CANTCALLOUT_AGAIN, record the interface, method, component version, thread, apartment, process, and correlation ID.
• RPC_E_CANTCALLOUT_AGAIN can be returned during DCOM security initialization, proxy/stub marshaling, OBJREF processing, and server object lifetime. For RPC_E_CANTCALLOUT_AGAIN, record the interface, method, component version, thread, apartment, process, and correlation ID.

The immediate focus for RPC_E_CANTCALLOUT_AGAIN is legacy OLE/DDE call control where code attempts a nested second outbound call on a channel already servicing one conversation. Keep RPC_E_CANTCALLOUT_AGAIN attached to that operation; the same numeric severity outside the owning API does not supply enough context.

Diagnostic sequence

• Capture the raw unsigned value 0x80010011 and symbolic name RPC_E_CANTCALLOUT_AGAIN before a language projection, exception wrapper, or generic COM helper replaces it.
• Identify the exact interface, method, callback, activation request, metadata query, access-control operation, or marshaling boundary that returned RPC_E_CANTCALLOUT_AGAIN.
• Reconstruct the operation timeline for RPC_E_CANTCALLOUT_AGAIN, including object creation, thread or apartment initialization, security setup, callbacks, mutations, shutdown, and cleanup.
• Prove the decisive condition: the active conversation, current outbound call, callback stack, and channel ownership are known.
• Inspect every output parameter, handle, interface pointer, token, SID, ACL, stream, buffer, server-side object, or asynchronous result produced before RPC_E_CANTCALLOUT_AGAIN.
• Reproduce RPC_E_CANTCALLOUT_AGAIN with the smallest safe input, change only the suspected precondition, and verify that both the HRESULT and postcondition change as predicted.

Evidence and telemetry

• Preserve DDE conversation and channel IDs for RPC_E_CANTCALLOUT_AGAIN.
• Preserve current and attempted call for RPC_E_CANTCALLOUT_AGAIN.
• Preserve callback depth for RPC_E_CANTCALLOUT_AGAIN.
• Preserve message sequence for RPC_E_CANTCALLOUT_AGAIN.
• Preserve queued follow-up result for RPC_E_CANTCALLOUT_AGAIN.

For RPC_E_CANTCALLOUT_AGAIN, also record UTC time, process and thread IDs, apartment type, component version, security or package identity where relevant, and a correlation ID. For RPC_E_CANTCALLOUT_AGAIN, use hashes, lengths, GUIDs, and SID strings rather than logging confidential payloads or credentials.

Correct handling and recovery

Return from the current call before issuing another, queue the follow-up operation, and remove reentrant DDE or OLE automation from callbacks.

An unchanged retry loop for RPC_E_CANTCALLOUT_AGAIN can duplicate effects, deepen reentrancy, or hide an invalid lifetime transition.

Difference from nearby HRESULTs

RPC_E_CANTCALLOUT_AGAIN is channel-specific nested call prevention; RPC_E_CANTCALLOUT_ININPUTSYNCCALL concerns outgoing COM calls during input-synchronous dispatch.

Merging RPC_E_CANTCALLOUT_AGAIN with the neighboring HRESULT would choose the wrong retry, recreation, authorization, or cleanup path.

Lifetime, retry, and cleanup rules

After RPC_E_CANTCALLOUT_AGAIN, determine whether the current object, interface pointer, call context, token, stream, metadata reader, asynchronous operation, or access-control instance remains valid. For RPC_E_CANTCALLOUT_AGAIN, 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 RPC_E_CANTCALLOUT_AGAIN should state the trigger, maximum attempts, cancellation owner, and reconciliation step for effects that may have completed elsewhere.

Developer and administrator guidance

When RPC_E_CANTCALLOUT_AGAIN crosses native, managed, scripting, RPC, or WinRT projection boundaries, preserve the unsigned 32-bit HRESULT. Unit tests for RPC_E_CANTCALLOUT_AGAIN should assert the code-specific postcondition and resource ownership, not merely that an exception was thrown.

Document the owner of the RPC_E_CANTCALLOUT_AGAIN boundary so future occurrences can be correlated across client, proxy, server, package, and security logs. Define who owns retry, cancellation, cleanup, policy changes, package repair, and user-facing messaging for RPC_E_CANTCALLOUT_AGAIN.

Practical scenario

An OLE container receives a DDE callback and immediately issues another command on the same conversation. It queues the command until the first exchange completes.

A regression test should reproduce RPC_E_CANTCALLOUT_AGAIN, 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 — official Microsoft documentation relevant to RPC_E_CANTCALLOUT_AGAIN.
• Microsoft: IMessageFilter — official Microsoft documentation relevant to RPC_E_CANTCALLOUT_AGAIN.
• Microsoft: RetryRejectedCall — official Microsoft documentation relevant to RPC_E_CANTCALLOUT_AGAIN.
• Microsoft: CoInitialize — official Microsoft documentation relevant to RPC_E_CANTCALLOUT_AGAIN.
• Microsoft: CoInitializeSecurity — official Microsoft documentation relevant to RPC_E_CANTCALLOUT_AGAIN.
• Microsoft: marshaling rules — official Microsoft documentation relevant to RPC_E_CANTCALLOUT_AGAIN.
• Microsoft: HRESULT values — official Microsoft documentation relevant to RPC_E_CANTCALLOUT_AGAIN.

Looking for a different code? Search another status or error code.