| Previous | Next |
| DB_S_TYPEINFOOVERRIDDEN | DB_S_NONEXTROWSET |
DB_S_BOOKMARKSKIPPED
OLE DB skipped a bookmark for a deleted or nonmember row
DB_S_BOOKMARKSKIPPED is HRESULT 265923 (0x00040EC3) from Microsoft OLE DB. AllStat describes this result as “Bookmark was skipped for deleted or nonmember row.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.
The rowset operation continued but did not return the row identified by a bookmark because that row was deleted or no longer belongs to the rowset.
Evidence and telemetry to preserve
- preserve bookmark bytes and source rowset identity.
- preserve rowset change model.
- preserve deleted-row notifications.
- preserve rows actually obtained.
- preserve next fetch position.
Also record db_s_bookmarkskipped_operation, db_s_bookmarkskipped_object, db_s_bookmarkskipped_state_before, db_s_bookmarkskipped_state_after, UTC time, process and thread identifiers, and a correlation ID. Keep secrets out of logs while retaining GUIDs, CLSIDs, media subtypes, property IDs, row identities, and hashes needed to distinguish objects.
Where the result is encountered
- This result can appear in IRowsetLocate and IRowsetFind; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- This result can appear in dynamic rowsets under concurrent updates; record the producing interface and method rather than inferring behavior from the symbolic name alone.
- It can appear in bookmark-based paging or resume logic; record the producing interface and method rather than inferring behavior from the symbolic name alone.
The same numeric success value can be mishandled when a wrapper exposes only a Boolean. Keep the original HRESULT until the code-specific outputs and state transition have been evaluated.
State boundary that must be proved
The central question for it is whether the consumer distinguishes a stale bookmark from end-of-rowset and continues from a defined position. The HRESULT alone confirms neither unrelated work nor the quality of optional outputs.
A reliable interpretation of it names the exact method contract, the object generation, and the outputs that remain valid. This prevents a success-with-information result from being promoted to full success or demoted to a generic error.
Diagnostic sequence
- capture the raw HRESULT
0x00040EC3immediately after the returning method and record whether the caller usedSUCCEEDED,FAILED, equality testing, or exception translation. - Identify the exact owner of it: interface, method, object instance, provider or filter version, thread or apartment, and operation phase.
- Validate the decisive contract boundary for it: the consumer distinguishes a stale bookmark from end-of-rowset and continues from a defined position.
- inspect every output parameter, count, status array, returned interface, or side effect that the method documentation associates with this success-with-information result.
- Compare the observed state before and after it; do not assume that a success severity bit means every optional sub-operation completed.
- reproduce the smallest request with the same object state and then change only the condition identified by the evidence before repeating the operation.
Difference from nearby HRESULT values
DB_S_BADROWHANDLE concerns an HROW; it concerns a bookmark whose row disappeared or left the membership set.
This distinction determines whether the caller should consume partial outputs, stop iteration, wait, reconfigure, notify the user, or perform no error recovery at all.
Correct handling, retry, and recovery
Discard or refresh the stale bookmark, process other returned rows, and obtain a new bookmark from the current rowset. Do not reuse bookmarks across unrelated rowset instances.
Retry it only when the recorded state can change the documented outcome. Repeating the same call is inappropriate for a stable end marker, cancellation, unsupported format, adjusted property, or partial result whose completed side effects have not been reconciled.
Practical validation scenario
A live result set is paged by bookmarks while another transaction deletes a row. The consumer logs the skipped bookmark, continues with remaining rows, and rebuilds its resume token.
The negative test should preserve the condition that produces it; the recovery test should alter only that condition and verify the final state as well as the HRESULT.
Developer and administrator guidance
Tests for it should verify both the encoded condition and the resulting outputs. A test for it that checks only SUCCEEDED cannot detect stale counts, partial streams, adjusted properties, missing callbacks, or other code-specific effects.
A support report for it should include decimal 265923, hexadecimal 0x00040EC3, the AllStat meaning, the owning API, and the first detailed status or output that explains why the method did not return ordinary S_OK.
References
- Microsoft: OLE DB return codes
- Microsoft: OLE DB Driver return codes
- Microsoft: OLE DB error records
- Microsoft: IRowsetLocate::GetRowsAt
Looking for a different code? Search another status or error code.