| Previous | Next |
| MD_E_INVALIDCELLRANGE | DB_E_COMMANDNOTPERSISTED |
DB_E_NOCOLUMN
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 this result is a failure HRESULT. Its facility is 4 (FACILITY_ITF) and its low code is 3685 (0x0E65). These fields identify an interface-defined result family; they do not identify the provider instance, method, object generation or partial effects.
Contract boundary
OLE DB distinguishes numeric ordinals, DBID-based column identifiers and per-column status. 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 this result should start with the current command result, rowset or row object and the metadata generation from which the column reference came. Capture it before ADO, ATL,.NET or a database abstraction layer replaces the native HRESULT with a generic exception.
Evidence to collect
A useful this result event records provider CLSID and version, process architecture, interface IID and method, object correlation ID, transaction state and the immediately preceding HRESULT. When recording it 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 it: the complete DBID kind and components.
- Evidence 2 for it: current column metadata for the object.
- Evidence 3 for it: schema version and object identity used to construct the DBID.
Conditions that specifically lead to it
- Cause 1 for it: the DBID name or GUID is wrong.
- Cause 2 for it: a row-object column ID is reused as a base-table column ID.
- Cause 3 for it: the column was removed or renamed after metadata was cached.
Diagnostic sequence
- Capture raw
0x80040E65and symbolic it at the native call boundary. - Identify the exact failing stage for it: a method receives a DBID that does not identify a column in the current row, rowset or schema scope.
- Retrieve all OLE DB error records for it before another COM call replaces thread error information.
- Compare the live object state and provider-granted capabilities with the input that produced it.
- Reduce the operation to the smallest case that preserves the same column contract.
- Apply one evidence-backed correction for it and verify that the result is not merely replaced by a neighboring HRESULT.
Retry and recovery
Retry rule for it: retry after supplying a DBID that current metadata identifies as a column. A it retry is safe only when the relevant input, object generation, capability or external state has changed. Before replaying a modifying call that returned it, determine whether rows, schema objects or URL resources were partially created or changed.
Do not turn it into an unbounded retry loop. Preserve cancellation for it and use a fresh provider object when the failed call may have left local state ambiguous.
Corrective actions
- Action 1 for it: use DBIDs returned for the exact target interface.
- Action 2 for it: rebuild IDs after schema changes.
- Action 3 for it: 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 it. Keeping it with the method and object state makes this scenario diagnosable instead of reducing it to “database error”.
Developer and operations guidance
Code handling it 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 it, opaque values such as HACCESSOR, HROW, HCHAPTER, DBID components and provider handles must remain scoped to the object that issued them.
Operational dashboards for it should group by provider version, interface, method and normalized failure stage. A it 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 it rejects a DBID. Telemetry and remediation for it should keep these outcomes distinct.
Official Microsoft references
Looking for a different code? Search another status or error code.