Site icon EfmSoft

What does HRESULT 0x8004020B (EVENT_E_NOT_ALL_REMOVED) mean?

 
Could be also:
ConstantTypeOS
VFW_E_RUNTIME_ERRORHRESULTWindows
Previous Next
VFW_E_NO_ALLOCATOR VFW_E_RUNTIME_ERROR

EVENT_E_NOT_ALL_REMOVED

Meaning and numerical form

EVENT_E_NOT_ALL_REMOVED is HRESULT 2147746315 (0x8004020B; signed -2147220981). Windows documents its meaning as “Not all the objects requested could be removed”. In practical terms, it is returned when a COM+ event-system remove operation deletes some requested objects but cannot remove every matching item.

The severity bit in 0x8004020B is set, so this result is a failure result rather than a success or informational status. Within the COM+ Events range, its facility is 4 (FACILITY_ITF) and its low 16-bit code is 523 (0x020B). Those fields classify the value but do not identify the component instance, call, object or input that produced it.

Evidence to collect

  • Capture 1: the removal query and initial matched object IDs.
  • Capture 2: which identifiers were removed and which remained.
  • Capture 3: per-object permissions, dependencies and catalog generation.

Where the failure belongs

This result belongs to COM+ Events catalog and delivery. COM+ Events separates publishers, event classes, subscriptions and subscribers through catalog records. A useful diagnosis therefore follows both the catalog relationship and the eventual subscriber invocation. The relevant condition is that a COM+ event-system remove operation deletes some requested objects but cannot remove every matching item.

Likely causes

  • Possible cause 1: one object is protected, in use or inaccessible.
  • Possible cause 2: the query matches objects across partitions or ownership boundaries.
  • Possible cause 3: concurrent catalog changes alter the result set during removal.

Diagnostic sequence

  1. Confirm that the observed path matches this condition: a COM+ event-system remove operation deletes some requested objects but cannot remove every matching item.

Correct handling and retry

  • Corrective action 1: treat the operation as partial completion and enumerate remaining objects.
  • Corrective action 2: remove dependencies in a controlled order.
  • Corrective action 3: report exact survivors instead of repeating a broad delete blindly.

Retry guidance. Retry only for the remaining object IDs after confirming why they were retained; repeating the original broad query can obscure partial progress. When retrying, avoid deliver an event twice, modify the wrong catalog object or hide partial subscriber completion.

Difference from nearby HRESULTs

EVENT_E_CANT_MODIFY_OR_DELETE_CONFIGURED_OBJECT rejects a specific configured object, while it is an aggregate partial-removal result.

Developer and operational guidance

Practical scenario

A cleanup command removes obsolete subscriptions but one configured object remains protected; enumerating the survivor explains it.

Official Microsoft references


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

Exit mobile version