| Previous | Next |
| DB_E_CHAPTERNOTRELEASED | DB_E_PARAMUNAVAILABLE |
DB_E_BADSOURCEHANDLE
Exact value and result class
DB_E_BADSOURCEHANDLE has unsigned value 2147749456 (0x80040E50) and signed 32-bit value -2147217840. AllStat describes it as “Source handle is invalid”. In this result, a provider receives a source handle that is invalid for the current source object or operation; the public text does not identify a single owning API.
The high bit is set, so this result is a failure HRESULT. Its facility is 4 (FACILITY_ITF) and its low code is 3664 (0x0E50). These fields identify an interface-defined result family; they do not identify the provider instance, method, object generation or partial effects.
Contract boundary
Storage-object access transfers COM interface pointers for long or object-valued data. Some providers allow only one live storage object for a row or source, and every returned handle or interface remains scoped to the object and operation that created it.
Investigation of this result should start with the row, source handle and every open ISequentialStream, IStream or provider-specific storage interface. Capture it before ADO, ATL,.NET or a database abstraction layer replaces the native HRESULT with a generic exception.
Conditions that specifically lead to the result
- Cause 1 for it: the handle was released or never initialized.
- Cause 2 for it: the handle belongs to another provider object or generation.
- Cause 3 for it: a numeric copy of a provider-owned handle crossed an invalid lifetime boundary.
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 BLOB contents, object URLs and storage metadata, use types, lengths, hashes or redacted identifiers rather than secrets or complete business data.
- Evidence 1 for it: the exact IID and method accepting the source handle.
- Evidence 2 for it: the object that originally issued the handle.
- Evidence 3 for it: creation, transfer and release events for that handle.
Diagnostic sequence
- Capture raw
0x80040E50and symbolic it at the native call boundary. - Identify the exact failing stage for it: a provider receives a source handle that is invalid for the current source object or operation; the public text does not identify a single owning API.
- 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 storage contract.
- Apply one evidence-backed correction for it and verify that the result is not merely replaced by a neighboring HRESULT.
Corrective actions
- Action 1 for it: treat the source handle as opaque and object-scoped.
- Action 2 for it: reacquire it from the current source object.
- Action 3 for it: remove serialization or cross-object caching of provider handles.
Retry and recovery
Retry rule for it: retry only with a freshly issued handle whose owner and lifetime are proven. 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.
Practical scenario
A cache stores a source handle after its view is rebuilt; reacquiring the handle from the new view prevents the invalid-source result. Keeping it with the method and object state makes this scenario diagnosable instead of reducing it to “database error”.
Difference from nearby HRESULT values
DB_E_BADROWHANDLE identifies an invalid HROW, while it refers to a different provider-defined source handle. Telemetry and remediation for it should keep these outcomes distinct.
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.