| Previous | Next |
| VFW_E_NOT_CONNECTED | VFW_E_NO_ALLOCATOR |
EVENT_E_MISSING_EVENTCLASS
Meaning
Windows documents EVENT_E_MISSING_EVENTCLASS as “A subscription cannot be stored unless its event type already exists”. In practical terms, it is returned when a subscription is being stored before its referenced COM+ registration class exists in the event catalog.
Where the failure belongs
This result belongs to COM+ Events catalog and delivery. COM+ Events separates publishers, class identityes, 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 subscription is being stored before its referenced COM+ event type exists in the event catalog.
Diagnostic sequence
- Confirm that the observed path matches this condition: a subscription is being stored before its referenced COM+ registration class exists in the event catalog.
Likely causes
- Possible cause 1: deployment creates subscriptions before registering the class identity.
- Possible cause 2: the event type was removed while subscriptions were retained.
- Possible cause 3: subscription metadata names the wrong EventClassID or partition.
Evidence to collect
- Capture 1: subscription ID and referenced registration class CLSID.
- Capture 2: catalog partition and event-class registration timestamp.
- Capture 3: deployment ordering and rollback records.
Correct handling and retry
- Corrective action 1: register and validate the class identity before storing subscriptions.
- Corrective action 2: make deployment rollback remove dependent subscriptions consistently.
- Corrective action 3: verify partition-scoped identifiers instead of assuming a global catalog view.
Retry guidance. Retry after the correct event type exists and is visible in the same catalog partition. When retrying, avoid deliver an event twice, modify the wrong catalog object or hide partial subscriber completion.
Practical scenario
A deployment script imports subscriber definitions before installing the registration class component; reversing that order removes it.
Developer and operational guidance
Difference from nearby HRESULTs
REGDB_E_CLASSNOTREG is generic COM activation metadata failure; it specifically concerns the COM+ Events catalog relationship required by a subscription.
Official Microsoft references
Looking for a different code? Search another status or error code.