| Previous | Next |
| VFW_E_ALREADY_COMMITTED | VFW_E_BUFFERS_OUTSTANDING |
EVENT_E_PER_USER_SID_NOT_LOGGED_ON
Meaning and numerical form
EVENT_E_PER_USER_SID_NOT_LOGGED_ON is HRESULT 2147746320 (0x80040210; signed -2147220976). AllStat records its meaning as “The owner of the PerUser subscription is not logged on to the system specified”. In practical terms, it is returned when a valid per-user subscription owner is not logged on to the system where COM+ Events is attempting delivery.
The severity bit in 0x80040210 is set, so this result is a failure result rather than a success or informational status. Its facility is 4 (FACILITY_ITF) and its low 16-bit code is 528 (0x0210). Those fields classify the value but do not identify the component instance, call, object or input that produced it.
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 it diagnosis therefore follows both the catalog relationship and the eventual subscriber invocation. The decisive condition is this: a valid per-user subscription owner is not logged on to the system where COM+ Events is attempting delivery. Record the first native producer instead of relying only on a framework exception translated several layers later.
Do not infer from this result alone that reinstalling, rebooting or repeating the whole workflow is appropriate. Because it 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 it: the event fires before the user session starts.
- Possible cause 2 for it: the owner logged off while a queued delivery remained.
- Possible cause 3 for it: delivery targets the wrong host for the user session.
Evidence to collect
A useful this result 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 it, preserve IErrorInfo, an inner HRESULT, Win32 status, device event or provider message when available.
- Capture 1 for it: owner SID and resolved account name.
- Capture 2 for it: interactive-session and logon-session state on the target system.
- Capture 3 for it: subscription delivery mode, host and event timestamp.
Telemetry for it should retain types, lengths, hashes, stable opaque identifiers and lifecycle generations while redacting content and credentials. This makes repeated incidents comparable without exposing subscription identities, event payloads, account SIDs or credentials.
Diagnostic sequence
- Capture it at the first native return and identify the exact object and method.
- Confirm that the observed path matches this the condition: a valid per-user subscription owner is not logged on to the system where COM+ Events is attempting delivery.
- compare the live state with the method contract before changing configuration.
- collect the code-specific evidence listed above and preserve any more specific preceding error.
- change one evidence-backed cause at a time, then repeat the smallest operation that can prove the correction.
- Add a regression check that distinguishes it from the related outcomes described below.
Correction and retry boundary
- Corrective action 1 for it: deliver only while the owning session is present or use an appropriate non-per-user subscription.
- Corrective action 2 for it: route events to the host where the user is logged on.
- Corrective action 3 for it: handle logoff by suspending or removing transient user-scoped subscriptions.
Retry guidance for it. Retry when the same owner is logged on and duplicate delivery is safe; otherwise retain or discard the event according to application policy. A it 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 it.
Practical scenario
A desktop subscriber remains registered after sign-out and a service publishes another event; session-aware subscription cleanup prevents it. The result scenario narrows the result to a reproducible contract boundary and supplies a concrete before-and-after test.
Difference from nearby HRESULTs
EVENT_E_INVALID_PER_USER_SID means the account SID cannot be resolved; this HRESULT uses a valid SID but requires an active logon session. Keep these outcomes separate in logs, exception mappings, user messages, dashboards and automated retry policy.
Developer and operational guidance
Code handling it should log the failed stage before cleanup, keep ownership and lifecycle transitions explicit, and avoid converting every failure into a generic message. Tests for it 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 it should use the COM+ Administration APIs, Component Services and the owning deployment package. Avoid unsupported configuration edits or component replacement unless evidence identifies that layer. Retain the original trace and a post-fix trace so the result can be attributed and the change reversed.
Official Microsoft references
Looking for a different code? Search another status or error code.