What does HRESULT 0x80040E23 (DB_E_DELETEDROW) mean?

 
Previous Next
DB_E_NOAGGREGATION DB_E_CANTFETCHBACKWARDS

DB_E_DELETEDROW

Row handle referred to a deleted row or a row marked for deletion

Exact value and interpretation

DB_E_DELETEDROW has the unsigned 32-bit value 2147749411 (0x80040E23) and the signed representation -2147217885. AllStat defines the result as “Row handle referred to a deleted row or a row marked for deletion”. In the concrete failure represented here, an HROW identifies a row that has been deleted or marked for deletion.

The high bit is set for DB_E_DELETEDROW, 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 3619 (0x0E23). Those bit fields place DB_E_DELETEDROW 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_DELETEDROW 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_DELETEDROW. Preserve DB_E_DELETEDROW 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_DELETEDROW: the consumer calls GetData after deleting the row.
  • Cause 2 for DB_E_DELETEDROW: another actor deleted the row and the dynamic rowset exposed the change.
  • Cause 3 for DB_E_DELETEDROW: deferred-update state marks the row deleted before transmission.

Evidence to collect before changing the system

A useful DB_E_DELETEDROW 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_DELETEDROW 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_DELETEDROW: the HROW and rowset generation.
  • Evidence 2 for DB_E_DELETEDROW: delete, notification and resynchronization events.
  • Evidence 3 for DB_E_DELETEDROW: pending-change status and transaction visibility.

Diagnostic sequence

  1. Capture DB_E_DELETEDROW 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_DELETEDROW: an HROW identifies a row that has been deleted or marked for deletion.
  3. For DB_E_DELETEDROW, compare the live command, rowset, accessor or schema state with the metadata and properties actually granted by the provider.
  4. For DB_E_DELETEDROW, 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_DELETEDROW, reproduce the issue with the smallest command, rowset or definition operation that preserves the same contract boundary.
  6. For DB_E_DELETEDROW, 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_DELETEDROW: stop using the row handle once deletion is observed.
  • Action 2 for DB_E_DELETEDROW: refresh or refetch the rowset when external deletes are expected.
  • Action 3 for DB_E_DELETEDROW: preserve delete state in the UI instead of treating the row as a generic invalid handle.

Retry and recovery policy

Retry rule for DB_E_DELETEDROW: retry only by locating a surviving row or undoing a pending deletion when the provider supports it. A safe DB_E_DELETEDROW retry must use a changed input, object generation, provider capability or state transition. If the call returning DB_E_DELETEDROW could have created, updated, deleted or copied data, determine partial completion before replaying it.

For DB_E_DELETEDROW, use bounded retries and preserve cancellation. For DB_E_DELETEDROW, 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 grid keeps a selected HROW after the user deletes that row and later requests its values; clearing the selection on the delete notification avoids DB_E_DELETEDROW. The diagnostic value comes from retaining DB_E_DELETEDROW together with the failing interface and object state, not from reducing every provider result to “database error”.

Difference from related HRESULT values

DB_E_BADROWHANDLE means the handle is invalid for the rowset, while DB_E_DELETEDROW means it refers to a known row that is deleted or pending deletion. Keep these outcomes separate in telemetry and user-facing remediation because DB_E_DELETEDROW requires a different next action.

Implementation guidance

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

When DB_E_DELETEDROW 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_DELETEDROW, 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.