What does HRESULT 0x80110820 (COMADMIN_E_CANNOT_ALIAS_EVENTCLASS) mean?

 
Previous Next
COMADMIN_E_BASEPARTITION_REQUIRED_IN_SET COMADMIN_E_PRIVATE_ACCESSDENIED

COMADMIN_E_CANNOT_ALIAS_EVENTCLASS

COMADMIN_E_CANNOT_ALIAS_EVENTCLASS is the failure HRESULT 0x80110820 (signed decimal -2146367456, unsigned decimal 2148599840). Its severity bit is 1, facility is 17 (FACILITY_ITF), and the facility-specific code field is 0x0820.

Event Class identity versus component aliases: exact meaning of COMADMIN_E_CANNOT_ALIAS_EVENTCLASS

The target component is a COM+ Event Class, and COM+ refuses to create an alias for it. Event Classes have publication identity and subscription semantics that cannot be safely duplicated through ordinary component aliasing.

AllStat records the Windows SDK description as “Alas, Event Class components cannot be aliased.”

Where COMADMIN_E_CANNOT_ALIAS_EVENTCLASS occurs

ICOMAdminCatalog2 alias creation has resolved the original component and detects its Event Class role before creating the alias CLSID/ProgID and catalog object.

Evidence to collect before changing the catalog

  • source CLSID, EventCLSID/EventClassName, type library, and component flags.
  • requested alias CLSID/ProgID and destination application.
  • publisher/subscriber configuration and existing subscriptions.
  • exact AliasComponent call and catalog state before the request.

Typical cause branches

  • automation applies alias creation uniformly to ordinary components and Event Classes.
  • an Event Class is mistaken for a normal subscriber or business component.
  • deployment tries to publish the same event contract under a second alias identity.
  • component metadata changed to Event Class after an alias plan was generated.

Diagnostic sequence for COMADMIN_E_CANNOT_ALIAS_EVENTCLASS

  • confirm the source component is registered as an Event Class.
  • identify why a second identity is desired—versioning, routing, or compatibility.
  • create and register a separate intentional Event Class when a distinct publication identity is required.
  • update publishers/subscriptions through supported COM+ Events administration.
  • verify event delivery without relying on component aliasing.

Practical administration scenario

A deployment aliases every component into a compatibility application, but one source CLSID is the Event Class used by several persistent subscriptions.

Retry and recovery

The alias operation remains unsupported for an Event Class. Recovery requires a separate event-class design or use of the existing identity.

Difference from nearby COMADMIN results

COMADMIN_E_PRIVATE_ACCESSDENIED concerns activation of private components; this result is not an access check. It rejects alias semantics for a specific component category.

What this HRESULT does not establish

The code does not mean the Event Class is invalid or cannot be versioned. It means ordinary COM+ component aliasing is not the supported versioning mechanism.

Developer and operations guidance

Record source EventCLSID/ProgID, requested alias IDs, type library, application/partition, subscription count, and deployment reason.

Official Microsoft references for COMADMIN_E_CANNOT_ALIAS_EVENTCLASS

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