What does HRESULT 0x8004020B (EVENT_E_NOT_ALL_REMOVED) mean?

EVENT_E_NOT_ALL_REMOVED

Not all the objects requested could be removed

Meaning and numerical form

EVENT_E_NOT_ALL_REMOVED is HRESULT 2147746315 (0x8004020B; signed -2147220981). For EVENT_E_NOT_ALL_REMOVED, AllStat records 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 EVENT_E_NOT_ALL_REMOVED 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). For EVENT_E_NOT_ALL_REMOVED, those fields classify the value but do not identify the component instance, call, object or input that produced it.

Evidence to collect

A useful EVENT_E_NOT_ALL_REMOVED record includes the native API or interface method, component or CLSID, process and thread IDs, architecture, apartment where relevant, operation correlation ID, elapsed time, input identity, and the first state-changing event before failure. When diagnosing EVENT_E_NOT_ALL_REMOVED, preserve IErrorInfo, an inner HRESULT, Win32 status, device event or provider message when available.

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

Telemetry for EVENT_E_NOT_ALL_REMOVED should retain types, lengths, hashes, stable opaque identifiers and lifecycle generations while redacting content and credentials. For EVENT_E_NOT_ALL_REMOVED, this makes repeated incidents comparable without exposing subscription identities, event payloads, account SIDs or credentials.

Where the failure belongs

EVENT_E_NOT_ALL_REMOVED belongs to COM+ Events catalog and delivery. For EVENT_E_NOT_ALL_REMOVED, COM+ Events separates publishers, event classes, subscriptions and subscribers through catalog records. A useful EVENT_E_NOT_ALL_REMOVED diagnosis therefore follows both the catalog relationship and the eventual subscriber invocation. For EVENT_E_NOT_ALL_REMOVED, the decisive condition is this: a COM+ event-system remove operation deletes some requested objects but cannot remove every matching item. For EVENT_E_NOT_ALL_REMOVED, record the first native producer instead of relying only on a framework exception translated several layers later.

Do not infer from EVENT_E_NOT_ALL_REMOVED alone that reinstalling, rebooting or repeating the whole workflow is appropriate. Because EVENT_E_NOT_ALL_REMOVED can cross process and language boundaries, its correction depends on the object identity, lifecycle generation, input and state at the first failing call.

Likely causes

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

Diagnostic sequence

1. Capture EVENT_E_NOT_ALL_REMOVED at the first native return and identify the exact object and method.
2. Confirm that the observed path matches this EVENT_E_NOT_ALL_REMOVED condition: a COM+ event-system remove operation deletes some requested objects but cannot remove every matching item.
3. For EVENT_E_NOT_ALL_REMOVED, compare the live state with the method contract before changing configuration.
4. For EVENT_E_NOT_ALL_REMOVED, collect the code-specific evidence listed above and preserve any more specific preceding error.
5. For EVENT_E_NOT_ALL_REMOVED, change one evidence-backed cause at a time, then repeat the smallest operation that can prove the correction.
6. Add a regression check that distinguishes EVENT_E_NOT_ALL_REMOVED from the related outcomes described below.

Correction and retry boundary

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

Retry guidance for EVENT_E_NOT_ALL_REMOVED. Retry only for the remaining object IDs after confirming why they were retained; repeating the original broad query can obscure partial progress. A EVENT_E_NOT_ALL_REMOVED retry must avoid this hazard: deliver an event twice, modify the wrong catalog object or hide partial subscriber completion. It must also preserve the evidence needed to locate the original producer of EVENT_E_NOT_ALL_REMOVED.

Difference from nearby HRESULTs

EVENT_E_CANT_MODIFY_OR_DELETE_CONFIGURED_OBJECT rejects a specific configured object, while EVENT_E_NOT_ALL_REMOVED is an aggregate partial-removal result. For EVENT_E_NOT_ALL_REMOVED, keep these outcomes separate in logs, exception mappings, user messages, dashboards and automated retry policy.

Developer and operational guidance

Code handling EVENT_E_NOT_ALL_REMOVED should log the failed stage before cleanup, keep ownership and lifecycle transitions explicit, and avoid converting every failure into a generic message. Tests for EVENT_E_NOT_ALL_REMOVED should cover the primary cause, one adjacent HRESULT and the retry boundary so a future change cannot turn a deterministic contract failure into an uncontrolled loop.

Operational repair for EVENT_E_NOT_ALL_REMOVED should use the COM+ Administration APIs, Component Services and the owning deployment package. For EVENT_E_NOT_ALL_REMOVED, avoid unsupported configuration edits or component replacement unless evidence identifies that layer. For EVENT_E_NOT_ALL_REMOVED, retain the original trace and a post-fix trace so the result can be attributed and the change reversed.

Practical scenario

A cleanup command removes obsolete subscriptions but one configured object remains protected; enumerating the survivor explains EVENT_E_NOT_ALL_REMOVED. The EVENT_E_NOT_ALL_REMOVED scenario narrows the result to a reproducible contract boundary and supplies a concrete before-and-after test.

Official Microsoft references

• Microsoft: generic COM error codes — official documentation relevant to EVENT_E_NOT_ALL_REMOVED.
• Microsoft: IEventSystem — official documentation relevant to EVENT_E_NOT_ALL_REMOVED.
• Microsoft: COM+ Events concepts — official documentation relevant to EVENT_E_NOT_ALL_REMOVED.

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