What does HRESULT 0x80040E22 (DB_E_NOAGGREGATION) mean?

 
Previous Next
DB_E_ERRORSOCCURRED DB_E_DELETEDROW

DB_E_NOAGGREGATION

Non-NULL controlling IUnknown was specified, and either the requested interface was not IUnknown, or the provider does not support COM aggregation

Exact value and interpretation

DB_E_NOAGGREGATION has the unsigned 32-bit value 2147749410 (0x80040E22) and the signed representation -2147217886. AllStat defines the result as “Non-NULL controlling IUnknown was specified, and either the requested interface was not IUnknown, or the provider does not support COM aggregation”. In the concrete failure represented here, OLE DB object creation is requested with COM aggregation parameters the provider or requested interface cannot support.

The high bit is set for DB_E_NOAGGREGATION, so it is a failure HRESULT rather than a success or informational status. Its facility field is 4 (FACILITY_ITF) and its low code is 3618 (0x0E22). Those bit fields place DB_E_NOAGGREGATION in an interface-defined family, but they do not reveal the provider, object identity, method, rowset generation or command state that produced it.

Evidence to collect before changing the system

A useful DB_E_NOAGGREGATION record includes provider CLSID and version, process architecture, interface and method, COM apartment and thread, object correlation ID, transaction state, and the first preceding HRESULT. When DB_E_NOAGGREGATION involves object URLs, command trees, data source names, caller identities and copied data, record types, lengths, hashes or redacted identifiers instead of secrets or full business data.

  • Evidence 1 for DB_E_NOAGGREGATION: pUnkOuter presence, requested IID and object type.
  • Evidence 2 for DB_E_NOAGGREGATION: provider documentation or properties for aggregation support.
  • Evidence 3 for DB_E_NOAGGREGATION: the exact creation method and returned interface request.

OLE DB contract boundary

DB_E_NOAGGREGATION must be interpreted against this contract: OLE DB objects follow both COM lifetime rules and provider-specific state contracts; open dependents, ownership transfer, aggregation, callbacks and namespace identity must be traced from the exact interface call rather than inferred from a wrapper exception.

Start with the COM object that returned the result and every dependent interface or provider-owned resource involved in the call when investigating DB_E_NOAGGREGATION. Preserve DB_E_NOAGGREGATION before ADO, ATL, .NET, a database abstraction layer or an application exception replaces it with a generic message; the exact interface and method matter because one OLE DB object can expose several contracts with different preconditions.

Specific conditions that produce this result

  • Cause 1 for DB_E_NOAGGREGATION: pUnkOuter is non-NULL but the provider does not support aggregation for the object.
  • Cause 2 for DB_E_NOAGGREGATION: the requested interface is not IID_IUnknown during aggregated creation.
  • Cause 3 for DB_E_NOAGGREGATION: the outer object does not follow COM controlling-IUnknown rules.

Diagnostic sequence

  1. Capture DB_E_NOAGGREGATION immediately at the native OLE DB return and obtain the current OLE DB error object before another COM call replaces thread error information.
  2. Identify the exact stage for DB_E_NOAGGREGATION: OLE DB object creation is requested with COM aggregation parameters the provider or requested interface cannot support.
  3. For DB_E_NOAGGREGATION, compare the live command, rowset, accessor or schema state with the metadata and properties actually granted by the provider.
  4. For DB_E_NOAGGREGATION, inspect per-binding, per-property, per-row or per-record statuses whenever the method supplies them; the aggregate result may not identify the rejected element.
  5. For DB_E_NOAGGREGATION, reproduce the issue with the smallest command, rowset or definition operation that preserves the same contract boundary.
  6. For DB_E_NOAGGREGATION, apply one evidence-backed correction, then verify that the operation succeeds and does not merely change into a nearby HRESULT.

Corrective actions

  • Action 1 for DB_E_NOAGGREGATION: pass NULL for pUnkOuter when aggregation is unnecessary.
  • Action 2 for DB_E_NOAGGREGATION: request IID_IUnknown first when COM aggregation rules require it.
  • Action 3 for DB_E_NOAGGREGATION: replace aggregation with containment when the provider does not support it.

Practical incident

A generic factory always supplies an outer unknown when opening rowsets, including providers that reject aggregation; using nonaggregated creation prevents DB_E_NOAGGREGATION. The diagnostic value comes from retaining DB_E_NOAGGREGATION together with the failing interface and object state, not from reducing every provider result to “database error”.

Implementation guidance

Code handling DB_E_NOAGGREGATION should release OLE DB resources in ownership order, preserve every provider error record, and log granted properties rather than only requested properties. When handling DB_E_NOAGGREGATION, handles such as HACCESSOR, HROW, HCHAPTER and provider-specific region tokens must never be treated as portable integers across object lifetimes.

When DB_E_NOAGGREGATION crosses an abstraction boundary, attach a stable correlation ID and structured fields for the native HRESULT, provider source, interface IID, method, object generation and operation phase. For DB_E_NOAGGREGATION, do not log passwords, access tokens, complete SQL text or unrestricted row values merely to make the event easier to search.

Retry and recovery policy

Retry rule for DB_E_NOAGGREGATION: retry after correcting the COM creation parameters; provider state will not make an invalid aggregation request valid. A safe DB_E_NOAGGREGATION retry must use a changed input, object generation, provider capability or state transition. If the call returning DB_E_NOAGGREGATION could have created, updated, deleted or copied data, determine partial completion before replaying it.

For DB_E_NOAGGREGATION, use bounded retries and preserve cancellation. For DB_E_NOAGGREGATION, configuration and contract failures should normally fail fast; concurrency, resource or transient state failures may justify retry only after their stated precondition changes.

Difference from related HRESULT values

CLASS_E_NOAGGREGATION is the general COM class-factory result, while DB_E_NOAGGREGATION is returned from an OLE DB object-creation contract. Keep these outcomes separate in telemetry and user-facing remediation because DB_E_NOAGGREGATION requires a different next action.

Official Microsoft references

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