What does HRESULT 0x80004029 (CO_E_ASYNC_WORK_REJECTED) mean?

 
Previous Next
CO_E_CLRNOTAVAILABLE CO_E_SERVER_INIT_TIMEOUT

CO_E_ASYNC_WORK_REJECTED

COM asynchronous work was rejected by the thread pool

CO_E_ASYNC_WORK_REJECTED is HRESULT 2147500073 (0x80004029) from winerror.h. AllStat describes it as “The thread-pool rejected the submitted asynchronous work.” The value must be interpreted at COM runtime work submitted to a thread pool during activation, cleanup, tracking, or callback dispatch, because the same high-level symptom can come from a different contract boundary and require different cleanup.

The decisive Interpretation is that the target thread pool would not accept the work item. The operational record for it needs the native value, symbolic constant, component build, and call phase; the message alone is insufficient.

Where the result appears

  • This result may surface in COM runtime work submitted to a thread pool during activation, cleanup, tracking, or callback dispatch.
  • The first boundary to preserve for it is the exact activation, initialization, call-control, or lifetime step that returned it.
  • record whether the failure occurred before an object identity existed, while a method was running, or during shutdown; those phases imply different ownership and retry rules.

Separate caller state from runtime and server state first; otherwise cleanup and retry may target the wrong generation of the operation.

Typical causes and interpretation boundary

Common cause categories for it are: the pool is closing; queue limits are exceeded; process shutdown has begun; callback environment is invalid. Each possible cause of this result predicts different outputs and recovery behavior, which should be verified explicitly.

The check that separates this result from nearby HRESULTs is: the target thread pool would not accept the work item. Without proof of the distinguishing condition for it, the safest action is to preserve evidence and refrain from destructive cleanup.

Correct handling and recovery

The appropriate recovery is to stop accepting new operations during shutdown, bound queue growth, use a valid callback environment, and retry only after a new healthy pool exists. Repeat the operation only after the failed condition has changed and the caller can distinguish a duplicate effect.

When it is returned, use the documented output contract and reconcile remote or persistent effects before replaying the request.

Practical scenario

A server continues scheduling cleanup after closing its pool; the shutdown sequence is reordered so producers stop before the pool closes.

An automated test for it should verify raw HRESULT, output ownership, cleanup behavior, and the absence of an unsafe automatic retry.

Difference from related HRESULTs

HRESULT_FROM_WIN32(ERROR_NOT_ENOUGH_QUOTA) can indicate resource pressure; this code specifically reports rejection by the asynchronous work facility.

The comparison matters operationally for it: one result may permit fallback while the other requires repair, cancellation, or state reconciliation.

Developer and administrator guidance

Code handling this result should classify it by lifecycle and ownership rather than by the high bit alone. For <code>it</code>, initialization failures normally require rebuilding the process or thread environment, capability results require a fallback, and uncertain remote outcomes require reconciliation before retry.

Operational dashboards should keep this result distinct from generic COM failures and attach deployment, service, package, runtime, policy, and architecture dimensions. Administrators should avoid broad registry edits, blanket firewall changes, or permission expansion unless the captured evidence for it identifies that subsystem.

References

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