What does HRESULT 0x80040E43 (DB_E_BOOKMARKSKIPPED) mean?

 
Previous Next
DB_E_BADRECORDNUM DB_E_BADPROPERTYVALUE

DB_E_BOOKMARKSKIPPED

Form of bookmark is valid, but no row was found to match it

Exact value and interpretation

DB_E_BOOKMARKSKIPPED has the unsigned 32-bit value 2147749443 (0x80040E43) and the signed representation -2147217853. AllStat defines the result as “Form of bookmark is valid, but no row was found to match it”. In the concrete failure represented here, a bookmark has a valid form but no row matching it is found in the current rowset.

The high bit is set for DB_E_BOOKMARKSKIPPED, 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 3651 (0x0E43). Those bit fields place DB_E_BOOKMARKSKIPPED in an interface-defined family, but they do not reveal the provider, object identity, method, rowset generation or command state that produced it.

Specific conditions that produce this result

  • Cause 1 for DB_E_BOOKMARKSKIPPED: the bookmarked row was deleted.
  • Cause 2 for DB_E_BOOKMARKSKIPPED: the row no longer satisfies the rowset filter.
  • Cause 3 for DB_E_BOOKMARKSKIPPED: the provider's bookmark persistence does not span the intervening change.

OLE DB contract boundary

DB_E_BOOKMARKSKIPPED must be interpreted against this contract: OLE DB rowsets own HROW values, fetch position, granted properties and visibility rules; row handles, bookmarks, update state and navigation capabilities remain valid only under the lifetime and generation that produced them.

Start with the current rowset instance, its granted properties and the exact row or position token used by the consumer when investigating DB_E_BOOKMARKSKIPPED. Preserve DB_E_BOOKMARKSKIPPED 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.

Diagnostic sequence

  1. Capture DB_E_BOOKMARKSKIPPED 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_BOOKMARKSKIPPED: a bookmark has a valid form but no row matching it is found in the current rowset.
  3. For DB_E_BOOKMARKSKIPPED, compare the live command, rowset, accessor or schema state with the metadata and properties actually granted by the provider.
  4. For DB_E_BOOKMARKSKIPPED, 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_BOOKMARKSKIPPED, reproduce the issue with the smallest command, rowset or definition operation that preserves the same contract boundary.
  6. For DB_E_BOOKMARKSKIPPED, apply one evidence-backed correction, then verify that the operation succeeds and does not merely change into a nearby HRESULT.

Evidence to collect before changing the system

A useful DB_E_BOOKMARKSKIPPED 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_BOOKMARKSKIPPED involves row values, bookmarks, keys and query parameters, record types, lengths, hashes or redacted identifiers instead of secrets or full business data.

  • Evidence 1 for DB_E_BOOKMARKSKIPPED: the bookmark length and safe hash.
  • Evidence 2 for DB_E_BOOKMARKSKIPPED: rowset filter, chapter and generation.
  • Evidence 3 for DB_E_BOOKMARKSKIPPED: delete or update notifications affecting the row.

Corrective actions

  • Action 1 for DB_E_BOOKMARKSKIPPED: treat the missing row as an absence outcome.
  • Action 2 for DB_E_BOOKMARKSKIPPED: refresh bookmarks after filtering or rowset replacement.
  • Action 3 for DB_E_BOOKMARKSKIPPED: use stable application keys when persistence beyond rowset lifetime is required.

Practical incident

A saved bookmark remains structurally valid after a row is filtered out, so GetRowsAt cannot match it; locating the row by application key avoids repeated DB_E_BOOKMARKSKIPPED. The diagnostic value comes from retaining DB_E_BOOKMARKSKIPPED together with the failing interface and object state, not from reducing every provider result to “database error”.

Retry and recovery policy

Retry rule for DB_E_BOOKMARKSKIPPED: retry only after obtaining a current bookmark or restoring a row that matches the rowset. A safe DB_E_BOOKMARKSKIPPED retry must use a changed input, object generation, provider capability or state transition. If the call returning DB_E_BOOKMARKSKIPPED could have created, updated, deleted or copied data, determine partial completion before replaying it.

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

Difference from related HRESULT values

DB_E_BADBOOKMARK means the bookmark bytes are invalid, while DB_E_BOOKMARKSKIPPED means the form is valid but no row matches. Keep these outcomes separate in telemetry and user-facing remediation because DB_E_BOOKMARKSKIPPED requires a different next action.

Implementation guidance

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

When DB_E_BOOKMARKSKIPPED 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_BOOKMARKSKIPPED, 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.