What does HRESULT 0x80040E2B (DB_E_NONCONTIGUOUSRANGE) mean?

 
Previous Next
DB_E_BADREGIONHANDLE DB_E_INVALIDTRANSITION

DB_E_NONCONTIGUOUSRANGE

Set of rows is not contiguous to, or does not overlap, the rows in the watch region

Exact value and interpretation

DB_E_NONCONTIGUOUSRANGE has the unsigned 32-bit value 2147749419 (0x80040E2B) and the signed representation -2147217877. AllStat defines the result as “Set of rows is not contiguous to, or does not overlap, the rows in the watch region”. In the concrete failure represented here, a requested set of rows neither forms a contiguous range nor overlaps the existing watch region as required.

The high bit is set for DB_E_NONCONTIGUOUSRANGE, 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 3627 (0x0E2B). Those bit fields place DB_E_NONCONTIGUOUSRANGE 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_NONCONTIGUOUSRANGE must be interpreted against this contract: OLE DB views and find operations derive row ranges from an accessor, comparison operators, current ordering and region state; handles and containment relationships become stale when the view, filter or rowset generation changes.

Start with the active rowset view, its criteria accessor and the region or row sequence supplied by the consumer when investigating DB_E_NONCONTIGUOUSRANGE. Preserve DB_E_NONCONTIGUOUSRANGE 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_NONCONTIGUOUSRANGE 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_NONCONTIGUOUSRANGE: a requested set of rows neither forms a contiguous range nor overlaps the existing watch region as required.
  3. For DB_E_NONCONTIGUOUSRANGE, compare the live command, rowset, accessor or schema state with the metadata and properties actually granted by the provider.
  4. For DB_E_NONCONTIGUOUSRANGE, 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_NONCONTIGUOUSRANGE, reproduce the issue with the smallest command, rowset or definition operation that preserves the same contract boundary.
  6. For DB_E_NONCONTIGUOUSRANGE, apply one evidence-backed correction, then verify that the operation succeeds and does not merely change into a nearby HRESULT.

Specific conditions that produce this result

  • Cause 1 for DB_E_NONCONTIGUOUSRANGE: the rows are supplied in discontinuous order.
  • Cause 2 for DB_E_NONCONTIGUOUSRANGE: the new range has a gap from the watch region.
  • Cause 3 for DB_E_NONCONTIGUOUSRANGE: stale row handles describe positions from a previous view ordering.

Evidence to collect before changing the system

A useful DB_E_NONCONTIGUOUSRANGE 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_NONCONTIGUOUSRANGE involves filter values, row keys, bookmarks and selection criteria, record types, lengths, hashes or redacted identifiers instead of secrets or full business data.

  • Evidence 1 for DB_E_NONCONTIGUOUSRANGE: the ordered row-handle list used to define the range.
  • Evidence 2 for DB_E_NONCONTIGUOUSRANGE: the current watch-region boundaries.
  • Evidence 3 for DB_E_NONCONTIGUOUSRANGE: sort and filter state that determines row adjacency.

Corrective actions

  • Action 1 for DB_E_NONCONTIGUOUSRANGE: construct ranges from the current view order.
  • Action 2 for DB_E_NONCONTIGUOUSRANGE: split disjoint selections into supported region operations.
  • Action 3 for DB_E_NONCONTIGUOUSRANGE: refresh handles after sort or filter changes.

Retry and recovery policy

Retry rule for DB_E_NONCONTIGUOUSRANGE: retry after supplying a contiguous or overlapping range under the current view ordering. A safe DB_E_NONCONTIGUOUSRANGE retry must use a changed input, object generation, provider capability or state transition. If the call returning DB_E_NONCONTIGUOUSRANGE could have created, updated, deleted or copied data, determine partial completion before replaying it.

For DB_E_NONCONTIGUOUSRANGE, use bounded retries and preserve cancellation. For DB_E_NONCONTIGUOUSRANGE, 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_NOTASUBREGION concerns containment, while DB_E_NONCONTIGUOUSRANGE concerns continuity or overlap of the supplied rows. Keep these outcomes separate in telemetry and user-facing remediation because DB_E_NONCONTIGUOUSRANGE requires a different next action.

Practical incident

A UI sends two separated selected blocks as one watch-region extension; issuing two supported operations avoids DB_E_NONCONTIGUOUSRANGE. The diagnostic value comes from retaining DB_E_NONCONTIGUOUSRANGE together with the failing interface and object state, not from reducing every provider result to “database error”.

Implementation guidance

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

When DB_E_NONCONTIGUOUSRANGE 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_NONCONTIGUOUSRANGE, 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.