| Previous | Next |
| CI_PROPSTORE_INCONSISTENCY | CI_E_ENUMERATION_STARTED |
CI_INCORRECT_VERSION
CI_INCORRECT_VERSION — 0xC0041821
A productive reading of wrong on-disk Indexing Service version begins at the component boundary where catalog data was created by an incompatible Indexing Service format version.
The contract behind the code
Catalog partitions, indexes, identifiers, merges, and on-disk versions are internal storage structures. In the context of wrong on-disk Indexing Service version, supported catalog administration and rebuild paths are safer than copying or editing individual files. Locate the first component changing state in this condition and distinguish later summary errors.
Important boundary. Version mismatch is deliberate compatibility protection, not proof of random bit corruption. Record the exact constant and returning API.
Diagnostic worksheet
| Incident fact | What it separates |
|---|---|
| Catalog format/service versions, creating host, restore/migration history, and current OS | Separates catalog state from source data, filter output, and client lifecycle. |
| Backup metadata and whether binaries were upgraded or rolled back | Provides a stable before/after comparison for rebuilding or correcting the index path. |
| Scope definitions and source-content availability | Shows whether the first inconsistency arose during filtering, storage, administration, or enumeration. |
| New empty catalog created by the current service | Ties the result to one catalog, source document, filter, or query object. |
Preserve catalog IDs, filter versions, source hashes, property types, and timestamps; document contents and user data normally need not leave the host.
Useful comparisons
- Open a copy with the creating version where supported. Keep source bytes, scope, filter version, and unrelated catalog settings fixed.
- Build a small current-version catalog from the same source. Use a copied catalog or a small disposable catalog when the test can rebuild derived state.
- Test the documented migration or rebuild path rather than editing version fields. Retain a known-good document or query so a broad catalog rebuild is not mistaken for repair of the reported failure.
Retry only after one controlled catalog, filter, source, query, or merge condition changed; reopening the service may create a new catalog generation and hide the original evidence.
Read the result in context
- Known-good comparison succeeds: isolate the production object or configuration associated with the failing operation.
- Same failure on the control: investigate the shared catalog, storage, filter-host, or query layer before changing source documents.
- Different status after one change: preserve both results; the first rejected condition was removed, but the operation is not yet proved complete.
A defensible fix
Correction: Rebuild or migrate the catalog using a supported version path and retain source content as authority. 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 the current service owns the rebuilt catalog and it remains readable after merge and restart. 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
Use these Microsoft references for the formal contract and combine them with the exact server or catalog evidence from the incident: 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 and catalog management — provides the architecture, format, or protocol context.
- Microsoft: Indexing Service configuration entries — supports the controlled verification criteria.
Looking for a different code? Search another status or error code.