| Previous | Next |
| DB_E_ALREADYINITIALIZED | DB_E_MAXPENDCHANGESEXCEEDED |
DB_E_NOTSUPPORTED
Exact value and result class
DB_E_NOTSUPPORTED has unsigned value 2147749459 (0x80040E53) and signed 32-bit value -2147217837. AllStat describes it as “Method is not supported by this provider”. In this result, the consumer invokes an optional OLE DB method or capability that the active provider object does not support.
The high bit is set, so this result is a failure HRESULT. Its facility is 4 (FACILITY_ITF) and its low code is 3667 (0x0E53). These fields identify an interface-defined result family; they do not identify the provider instance, method, object generation or partial effects.
Contract boundary
Accessors are created on a specific command or rowset and encode direction, purpose, bound parts and buffer ownership. A valid HACCESSOR on one object is not interchangeable with a parameter accessor, a readable row accessor or an accessor created for another generation.
Investigation of this result should start with the object that created the accessor, its DBACCESSORFLAGS and every DBBINDING entry. Capture it before ADO, ATL,.NET or a database abstraction layer replaces the native HRESULT with a generic exception.
Diagnostic sequence
- Capture raw
0x80040E53and symbolic this result at the native call boundary. - Identify the exact failing stage for it: the consumer invokes an optional OLE DB method or capability that the active provider object does not support.
- 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 accessor contract.
- Apply one evidence-backed correction for it and verify that the result is not merely replaced by a neighboring HRESULT.
Conditions that specifically lead to it
- Cause 1 for it: the interface exists but the particular method path is optional.
- Cause 2 for it: the requested feature was assumed from another provider.
- Cause 3 for it: capability properties were requested but not actually granted.
Evidence to collect
A useful it 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 parameter values, row values and provider-owned storage pointers, use types, lengths, hashes or redacted identifiers rather than secrets or complete business data.
- Evidence 1 for it: provider CLSID and version.
- Evidence 2 for it: the exact interface and method.
- Evidence 3 for it: relevant granted properties and QueryInterface results.
Corrective actions
- Action 1 for it: feature-detect the operation on the active object.
- Action 2 for it: use a documented fallback with equivalent semantics.
- Action 3 for it: fail explicitly when no safe fallback preserves the contract.
Retry and recovery
Retry rule for it: retry only after selecting a provider, object type or feature path that reports support. 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.
Difference from nearby HRESULT values
E_NOINTERFACE means the interface itself is unavailable, while it can reject a method or operation within the OLE DB contract. Telemetry and remediation for it should keep these outcomes distinct.
Practical scenario
A data layer assumes every provider supports asynchronous binding; capability negotiation selects a synchronous path instead. 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.
Official Microsoft references
Looking for a different code? Search another status or error code.