| Previous | Next |
| CI_INVALID_PRIORITY | CI_OUT_OF_INDEX_IDS |
CI_NO_STARTING_KEY
CI_NO_STARTING_KEY — 0xC0041804
The built-in message is only the immediate status; the useful boundary is that an index traversal or query enumeration was started without the key needed to establish its initial position.
Start at the returning layer
Indexing Service query objects and enumerations have explicit configuration and lifecycle boundaries. In the context of missing starting key for index enumeration, catalog selection, code page, query text, start keys, object reuse, and the first fetch should be logged as one operation. Locate the first component changing state in missing starting key for index enumeration and distinguish later summary errors.
Important boundary. This is not the same as an empty result set; the traversal could not establish its starting position. Record the exact constant and returning API.
Minimum useful evidence
| Incident fact | What it separates |
|---|---|
| Returning helper/API, catalog, query, sort order, and key data | Ties the result to one catalog, source document, filter, or query object. |
| Whether enumeration was resumed from a saved bookmark or started fresh | Separates catalog state from source data, filter output, and client lifecycle. |
| Key column types and serialization | Provides a stable before/after comparison for rebuilding or correcting the index path. |
| Known-good enumeration with an explicitly initialized start key | Shows whether the first inconsistency arose during filtering, storage, administration, or enumeration. |
Preserve the smallest reproducible evidence set and remove document content or access-control details before sharing diagnostics.
Separate state from data
- Start a new enumeration with the documented initial key. Retain a known-good document or query so a broad catalog rebuild is not mistaken for repair of the reported failure.
- Compare fresh enumeration with resume/bookmark mode. Record the first filter, catalog, merge, query, or enumeration result that changes.
- Validate key column count and data types before dispatch. Keep source bytes, scope, filter version, and unrelated catalog settings fixed.
Do not use repeated enumeration or service restarts as the main test; a later success can reflect a fresh query object, completed merge, restarted filter host, or rebuilt derived state.
Nearby states and false leads
| Observed comparison | Interpretation |
|---|---|
| A known-good object succeeds through the same component | The platform path exists; concentrate on the production object, identity, metadata, or state captured above. |
| The control fails at the same first operation | Preserve catalog, storage, filter-host, source, and query evidence before modifying indexed documents. |
| The status changes after one deliberate adjustment | The diagnostic boundary moved; the replacement status now describes the next contract to investigate. |
Verification after correction
Correction: Initialize or persist the start key according to the selected enumeration mode and sort definition. Keep the original catalog configuration, source inventory, filter identity, query definition, and event sequence so the change can be reversed and explained.
Accept the repair only when fresh and resumed enumerations begin at deterministic positions and empty catalogs return normal end-of-enumeration status. Repeat the original supported operation under the original identity and object state; a new catalog, different source scope, or replacement filter is useful comparison evidence but not final regression proof.
Technical references
The following primary Microsoft documentation defines the status family and component boundaries used here: Check version-specific behavior against the Windows and Indexing Service generation that produced the result.
- Microsoft: Indexing Service purpose and architecture — defines the formal status or component boundary.
- Microsoft: Indexing Service helper-function values — documents the relevant API or lifecycle.
- Microsoft: Indexing Service query objects — provides the architecture, format, or protocol context.
- Microsoft: indexing and catalog management — supports the controlled verification criteria.
Looking for a different code? Search another status or error code.