| Previous | Next |
| VFW_E_ALREADY_CONNECTED | VFW_E_FILTER_ACTIVE |
EVENT_E_INTERNALEXCEPTION
Meaning
Windows documents EVENT_E_INTERNALEXCEPTION as “An unexpected exception was raised”. In practical terms, it is returned when the COM+ Events infrastructure catches an unexpected exception while performing internal event-system work.
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 the COM+ Events infrastructure catches an unexpected exception while performing internal event-system work.
Diagnostic sequence
- Confirm that the observed path matches this condition: the COM+ Events infrastructure catches an unexpected exception while performing internal event-system work.
Likely causes
- Possible cause 1: catalog access or event-system implementation raises an unexpected exception.
- Possible cause 2: marshaled data violates an internal assumption.
- Possible cause 3: a plug-in or filter crosses an exception boundary not represented by a normal HRESULT.
Evidence to collect
- Capture 1: the first exception code and COM error information.
- Capture 2: event class and subscription identifiers involved at the time.
- Capture 3: Component Services and application event logs around the same correlation ID.
Correct handling and retry
- Corrective action 1: preserve the original exception evidence before restarting services.
- Corrective action 2: repair catalog or component corruption indicated by supported diagnostics.
- Corrective action 3: escalate reproducible infrastructure faults with a minimal event-class and subscription export.
Retry guidance. Retry once after verifying service health when evidence suggests a transient infrastructure fault; repeated exceptions require investigation, not a loop. When retrying, avoid deliver an event twice, modify the wrong catalog object or hide partial subscriber completion.
Practical scenario
A malformed publisher-filter component throws across the event-system boundary; disabling that filter and correcting its exception handling removes it.
Developer and operational guidance
Operational repair 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.
Difference from nearby HRESULTs
EVENT_E_USER_EXCEPTION attributes the exception to user-supplied code; it attributes it to internal event processing.
Official Microsoft references
Looking for a different code? Search another status or error code.