What does HRESULT 0x80040E65 (DB_E_NOCOLUMN) mean?

 
Previous Next
MD_E_INVALIDCELLRANGE DB_E_COMMANDNOTPERSISTED

DB_E_NOCOLUMN

Column ID is invalid

Exact value and result class

DB_E_NOCOLUMN has unsigned value 2147749477 (0x80040E65) and signed 32-bit value -2147217819. AllStat describes it as “Column ID is invalid”. In this result, a method receives a DBID that does not identify a column in the current row, rowset or schema scope.

The high bit is set, so DB_E_NOCOLUMN is a failure HRESULT. Its facility is 4 (FACILITY_ITF) and its low code is 3685 (0x0E65). For DB_E_NOCOLUMN, these fields identify an interface-defined result family; they do not identify the provider instance, method, object generation or partial effects.

Contract boundary

For DB_E_NOCOLUMN, OLE DB distinguishes numeric ordinals, DBID-based column identifiers and per-column status. For DB_E_NOCOLUMN, metadata from IColumnsInfo or a row object is authoritative for the current result shape; cached identifiers can become invalid after command, schema or projection changes.

Investigation of DB_E_NOCOLUMN should start with the current command result, rowset or row object and the metadata generation from which the column reference came. Capture DB_E_NOCOLUMN before ADO, ATL, .NET or a database abstraction layer replaces the native HRESULT with a generic exception.

Evidence to collect

A useful DB_E_NOCOLUMN event records provider CLSID and version, process architecture, interface IID and method, object correlation ID, transaction state and the immediately preceding HRESULT. When recording DB_E_NOCOLUMN data involving column names, row values and query projections, use types, lengths, hashes or redacted identifiers rather than secrets or complete business data.

  • Evidence 1 for DB_E_NOCOLUMN: the complete DBID kind and components.
  • Evidence 2 for DB_E_NOCOLUMN: current column metadata for the object.
  • Evidence 3 for DB_E_NOCOLUMN: schema version and object identity used to construct the DBID.

Conditions that specifically lead to this result

  • Cause 1 for DB_E_NOCOLUMN: the DBID name or GUID is wrong.
  • Cause 2 for DB_E_NOCOLUMN: a row-object column ID is reused as a base-table column ID.
  • Cause 3 for DB_E_NOCOLUMN: the column was removed or renamed after metadata was cached.

Diagnostic sequence

  1. Capture raw 0x80040E65 and symbolic DB_E_NOCOLUMN at the native call boundary.
  2. Identify the exact failing stage for DB_E_NOCOLUMN: a method receives a DBID that does not identify a column in the current row, rowset or schema scope.
  3. Retrieve all OLE DB error records for DB_E_NOCOLUMN before another COM call replaces thread error information.
  4. Compare the live object state and provider-granted capabilities with the input that produced DB_E_NOCOLUMN.
  5. Reduce the DB_E_NOCOLUMN operation to the smallest case that preserves the same column contract.
  6. Apply one evidence-backed correction for DB_E_NOCOLUMN and verify that the result is not merely replaced by a neighboring HRESULT.

Retry and recovery

Retry rule for DB_E_NOCOLUMN: retry after supplying a DBID that current metadata identifies as a column. A DB_E_NOCOLUMN retry is safe only when the relevant input, object generation, capability or external state has changed. Before replaying a modifying call that returned DB_E_NOCOLUMN, determine whether rows, schema objects or URL resources were partially created or changed.

Do not turn DB_E_NOCOLUMN into an unbounded retry loop. Preserve cancellation for DB_E_NOCOLUMN and use a fresh provider object when the failed call may have left local state ambiguous.

Corrective actions

  • Action 1 for DB_E_NOCOLUMN: use DBIDs returned for the exact target interface.
  • Action 2 for DB_E_NOCOLUMN: rebuild IDs after schema changes.
  • Action 3 for DB_E_NOCOLUMN: avoid translating column names without provider identifier rules.

Practical scenario

A schema editor uses a result-set column DBID in IAlterTable; resolving the base column ID prevents DB_E_NOCOLUMN. Keeping DB_E_NOCOLUMN with the method and object state makes this scenario diagnosable instead of reducing it to “database error”.

Developer and operations guidance

Code handling DB_E_NOCOLUMN should release COM objects in ownership order, retain per-row, per-column or per-property statuses, and log granted capabilities rather than only requested options. While handling DB_E_NOCOLUMN, opaque values such as HACCESSOR, HROW, HCHAPTER, DBID components and provider handles must remain scoped to the object that issued them.

Operational dashboards for DB_E_NOCOLUMN should group by provider version, interface, method and normalized failure stage. A DB_E_NOCOLUMN event must not expose passwords, tokens, full connection strings, unrestricted command text or raw row contents.

Difference from nearby HRESULT values

DB_E_BADORDINAL rejects a numeric column position, while DB_E_NOCOLUMN rejects a DBID. Telemetry and remediation for DB_E_NOCOLUMN should keep these outcomes distinct.

Official Microsoft references

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