What does HRESULT 0x80040110 (CLASS_E_NOAGGREGATION) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The requested COM class cannot be created with the supplied controlling unknown.

Previous	Next
DRAGDROP_E_CONCURRENT_DRAG_ATTEMPTED	CLASS_E_CLASSNOTAVAILABLE

CLASS_E_NOAGGREGATION

Class does not support aggregation (or class object is remote)

Windows defines CLASS_E_NOAGGREGATION as 2147746064 (0x80040110; signed value -2147221232). AllStat’s description is “Class does not support aggregation (or class object is remote)”. The code marks a specific failure: The requested COM class cannot be created with the supplied controlling unknown. The relevant operation is IClassFactory::CreateInstance or CreateInstanceLic with non-null pUnkOuter.

The high bit in 0x80040110 is set, so this is a failure rather than a success or informational result. Its facility field is 4 (FACILITY_ITF) and its low 16-bit code is 272 (0x0110). Those bit fields classify the value, but they do not identify the failing object by themselves; the native method, object identity, and first producer of this result remain essential.

Where it is raised

Understanding this result requires this subsystem context: A COM class factory separates discovery of a class object from creation of an instance. Keeping those stages distinct reveals whether the defect is registration, factory selection, aggregation, licensing, or server implementation.

Associate this result with one exact operation in CoGetClassObject, IClassFactory::CreateInstance, aggregation rules, class availability, and optional licensing.
Confirm that this result came from IClassFactory::CreateInstance or CreateInstanceLic with non-null pUnkOuter, rather than from cleanup or a wrapper that ran afterward.
Preserve any IErrorInfo, underlying Win32 result, provider message, or callback failure that preceded it; the HRESULT alone should not erase a more specific cause.

Telemetry checklist

A useful incident records the CLSID, requested IID, class context, server path, pUnkOuter value, factory interface, activation machine, license path, and the first server-side return. Also retain the application and component build, architecture, process and thread IDs, COM apartment, operation correlation ID, elapsed time, and the first state-changing event before the failure. When logging it, redact content and credentials while preserving types, lengths, hashes, opaque identities, and lifecycle generations needed to reproduce its contract.

record whether pUnkOuter is null and which identity owns it.
verify the aggregation rule that the initial riid must be IID_IUnknown.
distinguish in-process aggregation from attempting to aggregate a remote class object.

Why it is specific

It can result when the class deliberately does not implement COM aggregation.
It can result when the caller passes pUnkOuter when it intended containment or delegation.
It can result when the request asks for an initial IID other than IUnknown during aggregation.

Investigation order

Capture it at the first native return before a wrapper maps it to a generic exception.
Identify the exact object, method, and lifecycle phase involved in IClassFactory::CreateInstance or CreateInstanceLic with non-null pUnkOuter.
Reproduce it with one controlled input or state change, and verify that the correction changes the decisive evidence rather than merely hiding the result.

Safe handling

Correction. for it, create the object nonaggregated, redesign the relationship as containment, or use a class explicitly documented to support aggregation. Retry boundary. Retry is valid only after changing pUnkOuter and the requested IID; repeated activation with the same outer object has no transient interpretation. Before repeating the operation, release any factory or partially initialized instance, determine whether a server process was launched, and avoid reusing a factory obtained before deployment or license state changed.

Practical scenario

A host passes its site object as pUnkOuter merely to receive callbacks; using a normal initialization interface after nonaggregated creation preserves separate identities. This isolates it within COM class factories and object creation and provides a regression test for the stated correction.

Difference from related HRESULTs

CLASS_E_CLASSNOTAVAILABLE means the factory cannot supply the class at all; it is specifically about the requested identity model. Keep those outcomes separate in exception mappings, telemetry dimensions, user messages, and automated retry policy.

Developer and administrator guidance

Keep class-object discovery separate from CreateInstance, log pUnkOuter and the initial IID, and make licensed creation an explicit IClassFactory2 path. Regression coverage for it should include in-process and local-server contexts, null and non-null controlling unknowns, IID_IUnknown aggregation rules, stale factories after upgrade, and valid versus missing license state.

Operational repair for it must target the evidence-backed owner: verify the registered server path and product version with the supported installer, and use the vendor’s licensing mechanism rather than copying registration or license material between machines. Retain before-and-after traces for it so the change can be attributed and reversed.

References

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