What does HRESULT 0x80040E49 (DB_E_NULLACCESSORNOTSUPPORTED) mean?

 
Previous Next
DB_E_BYREFACCESSORNOTSUPPORTED DB_E_NOTPREPARED

DB_E_NULLACCESSORNOTSUPPORTED

Null accessors are not supported by this provider

Exact value and interpretation

DB_E_NULLACCESSORNOTSUPPORTED has the unsigned 32-bit value 2147749449 (0x80040E49) and the signed representation -2147217847. AllStat defines the result as “Null accessors are not supported by this provider”. In the concrete failure represented here, the consumer attempts to create or use a null accessor with zero bindings, but the provider does not support that accessor form.

The high bit is set for DB_E_NULLACCESSORNOTSUPPORTED, 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 3657 (0x0E49). Those bit fields place DB_E_NULLACCESSORNOTSUPPORTED in an interface-defined family, but they do not reveal the provider, object identity, method, rowset generation or command state that produced it.

OLE DB contract boundary

DB_E_NULLACCESSORNOTSUPPORTED must be interpreted against this contract: OLE DB accessors describe how columns or parameters map to a consumer buffer; an HACCESSOR is object-scoped, reference-counted and inseparable from its DBBINDING layout, bound parts, data types, offsets and ownership rules.

Start with the command or rowset that created the accessor and the consumer buffer passed to the failing method when investigating DB_E_NULLACCESSORNOTSUPPORTED. Preserve DB_E_NULLACCESSORNOTSUPPORTED 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.

Diagnostic sequence

  1. Capture DB_E_NULLACCESSORNOTSUPPORTED 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_NULLACCESSORNOTSUPPORTED: the consumer attempts to create or use a null accessor with zero bindings, but the provider does not support that accessor form.
  3. For DB_E_NULLACCESSORNOTSUPPORTED, compare the live command, rowset, accessor or schema state with the metadata and properties actually granted by the provider.
  4. For DB_E_NULLACCESSORNOTSUPPORTED, 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_NULLACCESSORNOTSUPPORTED, reproduce the issue with the smallest command, rowset or definition operation that preserves the same contract boundary.
  6. For DB_E_NULLACCESSORNOTSUPPORTED, apply one evidence-backed correction, then verify that the operation succeeds and does not merely change into a nearby HRESULT.

Specific conditions that produce this result

  • Cause 1 for DB_E_NULLACCESSORNOTSUPPORTED: CreateAccessor is called with no bindings for a provider that requires at least one.
  • Cause 2 for DB_E_NULLACCESSORNOTSUPPORTED: a metadata-only path creates an accessor unnecessarily.
  • Cause 3 for DB_E_NULLACCESSORNOTSUPPORTED: a generic insert or fetch routine uses a null accessor as a sentinel.

Evidence to collect before changing the system

A useful DB_E_NULLACCESSORNOTSUPPORTED 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_NULLACCESSORNOTSUPPORTED involves parameter values, row contents, connection-specific identifiers and long-data buffers, record types, lengths, hashes or redacted identifiers instead of secrets or full business data.

  • Evidence 1 for DB_E_NULLACCESSORNOTSUPPORTED: the accessor flags and zero binding count.
  • Evidence 2 for DB_E_NULLACCESSORNOTSUPPORTED: the method that intended to use the accessor.
  • Evidence 3 for DB_E_NULLACCESSORNOTSUPPORTED: provider behavior for operations that need no bound data.

Corrective actions

  • Action 1 for DB_E_NULLACCESSORNOTSUPPORTED: omit the accessor-dependent call when no data is required.
  • Action 2 for DB_E_NULLACCESSORNOTSUPPORTED: bind the minimal real columns needed by the operation.
  • Action 3 for DB_E_NULLACCESSORNOTSUPPORTED: use the API's documented null-handle path when available instead of manufacturing a null accessor.

Retry and recovery policy

Retry rule for DB_E_NULLACCESSORNOTSUPPORTED: retry after removing the null accessor or creating a supported nonempty accessor. A safe DB_E_NULLACCESSORNOTSUPPORTED retry must use a changed input, object generation, provider capability or state transition. If the call returning DB_E_NULLACCESSORNOTSUPPORTED could have created, updated, deleted or copied data, determine partial completion before replaying it.

For DB_E_NULLACCESSORNOTSUPPORTED, use bounded retries and preserve cancellation. For DB_E_NULLACCESSORNOTSUPPORTED, 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

DB_E_BADACCESSORFLAGS rejects invalid flags, while DB_E_NULLACCESSORNOTSUPPORTED rejects the zero-binding accessor concept itself. Keep these outcomes separate in telemetry and user-facing remediation because DB_E_NULLACCESSORNOTSUPPORTED requires a different next action.

Practical incident

A generic row reader creates an accessor even when the projection is empty; skipping data transfer avoids DB_E_NULLACCESSORNOTSUPPORTED. The diagnostic value comes from retaining DB_E_NULLACCESSORNOTSUPPORTED together with the failing interface and object state, not from reducing every provider result to “database error”.

Implementation guidance

Code handling DB_E_NULLACCESSORNOTSUPPORTED 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_NULLACCESSORNOTSUPPORTED, handles such as HACCESSOR, HROW, HCHAPTER and provider-specific region tokens must never be treated as portable integers across object lifetimes.

When DB_E_NULLACCESSORNOTSUPPORTED 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_NULLACCESSORNOTSUPPORTED, do not log passwords, access tokens, complete SQL text or unrestricted row values merely to make the event easier to search.

Official Microsoft references

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