EVENT_S_SOME_SUBSCRIBERS_FAILED: meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

EVENT_S_SOME_SUBSCRIBERS_FAILED reports that COM+ delivered the event to some subscribers while one or more other subscriber calls failed.

Previous	Next
MK_S_MONIKERALREADYREGISTERED	EVENT_S_NOSUBSCRIBERS

EVENT_S_SOME_SUBSCRIBERS_FAILED

COM+ event reached only some subscribers

EVENT_S_SOME_SUBSCRIBERS_FAILED is HRESULT 262656 (0x00040200) from winerror.h. The documented description is “An event was able to invoke some but not all of the subscribers.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.

The event publication completed, but one or more subscribers failed while at least one other subscriber was invoked successfully.

Evidence to preserve

Preserve event class and interface method.
Preserve subscriber CLSIDs or identities.
Preserve per-subscriber HRESULT and error information.
Preserve delivery order and transaction context.
Preserve idempotency key or event correlation ID.

Where the result is encountered

This result can appear in COM+ loosely coupled events; record the producing interface and method.
This result can appear in publisher calls through an event class; record the producing interface and method.
It can appear in multi-subscriber notification where delivery results differ; record the producing interface and method.

State to verify

The central question is whether the publisher knows which subscriber effects occurred before deciding whether retry is safe.

Diagnostic sequence

Capture the raw HRESULT 0x00040200 immediately after the returning method and record whether the caller used SUCCEEDED, FAILED, equality testing, or exception translation.
Verify the method-specific state: the publisher knows which subscriber effects occurred before deciding whether retry is safe.

Difference from nearby HRESULT values

EVENT_S_NOSUBSCRIBERS reports an empty subscriber set; it reports a mixed delivery outcome.

Correct handling, retry, and recovery

Do not republish blindly because successful subscribers may run twice. Retry failed subscribers through a deduplicated mechanism or reconcile the event state explicitly.

Practical validation scenario

A configuration event has five subscribers; four update successfully and one is offline. The publisher records the failed subscriber, queues a targeted retry with the event ID, and does not redeliver to the four completed consumers.

Developer and administrator guidance

References

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