| Previous | Next |
| ERROR_VERSION_PARSE_ERROR | ERROR_MEMORY_HARDWARE |
ERROR_BADSTARTPOSITION
the iterator or rowset start position is invalid for the requested operation.
ERROR_BADSTARTPOSITION identifies this condition: The caller supplied a starting bookmark, offset, or cursor position that the provider cannot use. It may be outside the result set, stale after data changes, or incompatible with the cursor type.
Where the result appears
- database rowset navigation.
- iterators over provider-managed collections.
- pagination using saved bookmarks.
- resume tokens after reconnect or transaction change.
What to collect
- Start token or bookmark identity.
- result-set generation and query parameters.
- requested direction and row count.
- whether the underlying data or transaction changed.
Handling and recovery
Restart from a validated position, preferably a stable key or provider-issued continuation token. Expire cached positions when the query, sort order, transaction, or underlying collection changes.
Common misinterpretation
Clamping an invalid position to zero can silently return the wrong page. Surface token expiration distinctly when resuming exactly matters.
References
Looking for a different code? Search another status or error code.