What does HRESULT 0x80040E19 (DB_E_NOTFOUND) mean?

 
Previous Next
DB_E_CANNOTRESTART DB_E_CANNOTFREE

DB_E_NOTFOUND

Object or data matching the name, range, or selection criteria was not found within the scope of this operation

Exact value and interpretation

DB_E_NOTFOUND has the unsigned 32-bit value 2147749401 (0x80040E19) and the signed representation -2147217895. AllStat defines the result as “Object or data matching the name, range, or selection criteria was not found within the scope of this operation”. In the concrete failure represented here, an OLE DB lookup, open, bind or selection operation finds no object or data matching the supplied criteria within its defined scope.

The high bit is set for DB_E_NOTFOUND, 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 3609 (0x0E19). Those bit fields place DB_E_NOTFOUND 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_NOTFOUND must be interpreted against this contract: OLE DB objects follow both COM lifetime rules and provider-specific state contracts; open dependents, ownership transfer, aggregation, callbacks and namespace identity must be traced from the exact interface call rather than inferred from a wrapper exception.

Start with the COM object that returned the result and every dependent interface or provider-owned resource involved in the call when investigating DB_E_NOTFOUND. Preserve DB_E_NOTFOUND 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.

Specific conditions that produce this result

  • Cause 1 for DB_E_NOTFOUND: the requested table, row, resource or named object does not exist.
  • Cause 2 for DB_E_NOTFOUND: catalog, schema, chapter or URL scope differs from the caller's assumption.
  • Cause 3 for DB_E_NOTFOUND: a prior delete, rename or transaction change removed the target.

Evidence to collect before changing the system

A useful DB_E_NOTFOUND 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_NOTFOUND involves object URLs, command trees, data source names, caller identities and copied data, record types, lengths, hashes or redacted identifiers instead of secrets or full business data.

  • Evidence 1 for DB_E_NOTFOUND: the exact selection criteria and search scope.
  • Evidence 2 for DB_E_NOTFOUND: catalog, schema, chapter, URL or parent object active at the call.
  • Evidence 3 for DB_E_NOTFOUND: provider error records and a control lookup using the same identity.

Diagnostic sequence

  1. Capture DB_E_NOTFOUND 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_NOTFOUND: an OLE DB lookup, open, bind or selection operation finds no object or data matching the supplied criteria within its defined scope.
  3. For DB_E_NOTFOUND, compare the live command, rowset, accessor or schema state with the metadata and properties actually granted by the provider.
  4. For DB_E_NOTFOUND, 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_NOTFOUND, reproduce the issue with the smallest command, rowset or definition operation that preserves the same contract boundary.
  6. For DB_E_NOTFOUND, apply one evidence-backed correction, then verify that the operation succeeds and does not merely change into a nearby HRESULT.

Corrective actions

  • Action 1 for DB_E_NOTFOUND: verify the target in the same provider scope used by the failing call.
  • Action 2 for DB_E_NOTFOUND: refresh names and identifiers after schema or namespace changes.
  • Action 3 for DB_E_NOTFOUND: treat absence as a distinct outcome when the API contract allows it.

Retry and recovery policy

Retry rule for DB_E_NOTFOUND: retry only after the target is created, renamed back, or searched under corrected scope. A safe DB_E_NOTFOUND retry must use a changed input, object generation, provider capability or state transition. If the call returning DB_E_NOTFOUND could have created, updated, deleted or copied data, determine partial completion before replaying it.

For DB_E_NOTFOUND, use bounded retries and preserve cancellation. For DB_E_NOTFOUND, configuration and contract failures should normally fail fast; concurrency, resource or transient state failures may justify retry only after their stated precondition changes.

Practical incident

A service verifies a table in the default catalog but opens it through a session whose current catalog differs; qualifying the DBID resolves DB_E_NOTFOUND. The diagnostic value comes from retaining DB_E_NOTFOUND together with the failing interface and object state, not from reducing every provider result to “database error”.

Difference from related HRESULT values

DB_E_NOTABLE specifically says a table does not exist, while DB_E_NOTFOUND is the broader no-match result for the operation's scope. Keep these outcomes separate in telemetry and user-facing remediation because DB_E_NOTFOUND requires a different next action.

Implementation guidance

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

When DB_E_NOTFOUND 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_NOTFOUND, 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.