| Previous | Next |
| CI_INVALID_INDEX | CI_INCORRECT_VERSION |
CI_PROPSTORE_INCONSISTENCY
CI_PROPSTORE_INCONSISTENCY — 0xC0041809
A productive reading of Indexing Service property-store inconsistency begins at the component boundary where the catalog property cache no longer agrees with the index/catalog state and the catalog is stopped to protect consistency.
What the status actually records
Indexing Service catalogs are derived from source documents, filter output, word lists, indexes, and a property store. In the context of Indexing Service property-store inconsistency, corruption is reported, preserve source data and catalog evidence, validate storage, and rebuild derived structures rather than modifying documents to match the damaged index. Locate the first component changing state in this condition and distinguish later summary errors.
Important boundary. This is not merely one missing property value; the service detected a catalog-wide consistency boundary. Record the exact constant and returning API.
Evidence before intervention
| Preserve | Why it matters |
|---|---|
| Catalog, property cache files, first inconsistent property/work ID, and service event | Shows whether the first inconsistency arose during filtering, storage, administration, or enumeration. |
| Cached-property configuration and IFilter output types | Ties the result to one catalog, source document, filter, or query object. |
| Recent crash, restore, merge, or disk error | Separates catalog state from source data, filter output, and client lifecycle. |
| Source documents and property definitions needed for rebuild | Provides a stable before/after comparison for rebuilding or correcting the index path. |
Preserve the smallest reproducible evidence set and remove document content or access-control details before sharing diagnostics.
A controlled diagnostic path
- Index the same files into a clean catalog with the same cached properties. Use a copied catalog or a small disposable catalog when the test can rebuild derived state.
- Compare IFilter property types against configured column definitions. Retain a known-good document or query so a broad catalog rebuild is not mistaken for repair of the reported failure.
- Restart only after preserving the stopped catalog and storage evidence. Record the first filter, catalog, merge, query, or enumeration result that changes.
Stop after the first comparison that moves the boundary and diagnose the replacement catalog or query status independently.
How to distinguish nearby outcomes
- 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.
Correction and acceptance criteria
Correction: Repair storage or filter/type defects and rebuild the property store/catalog from authoritative documents. 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 cached properties query correctly after merge/restart and the catalog no longer stops itself. 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.