| Previous | Next |
| MSG_CI_MASTER_MERGE_CANT_RESTART | FILTER_E_CONTENTINDEXCORRUPT |
QUTIL_E_INVALID_CODEPAGE
QUTIL_E_INVALID_CODEPAGE — 0xC0041678
This result belongs to Indexing Service query code page not to a generic restart checklist, because the requested CiCodepage value is not accepted for parsing or converting the query input.
What the status actually records
Indexing Service query objects and enumerations have explicit configuration and lifecycle boundaries. In the context of Indexing Service query code page, 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 this condition and distinguish later summary errors.
Important boundary. An invalid code-page identifier is different from valid encoding with malformed query syntax. Record the exact constant and returning API.
Evidence before intervention
| Preserve | Why it matters |
|---|---|
| Raw query bytes, declared CiCodepage, locale, client API, and server version | Ties the result to one catalog, source document, filter, or query object. |
| Whether input is Unicode or converted from a legacy encoding | Separates catalog state from source data, filter output, and client lifecycle. |
| Characters near the first parse failure and replacement-character evidence | Provides a stable before/after comparison for rebuilding or correcting the index path. |
| Known-good query submitted with the documented default or Unicode path | Shows whether the first inconsistency arose during filtering, storage, administration, or enumeration. |
Preserve catalog IDs, filter versions, source hashes, property types, and timestamps; document contents and user data normally need not leave the host.
A controlled diagnostic path
- Submit an ASCII-only control under the same code page. Keep source bytes, scope, filter version, and unrelated catalog settings fixed.
- Convert the query to Unicode before calling the service. Use a copied catalog or a small disposable catalog when the test can rebuild derived state.
- Test one supported code page that can represent the query text. 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.
How to distinguish nearby outcomes
When a minimal control succeeds, the failure is tied to the original object or its state rather than to the whole Windows subsystem. When the control fails identically, preserve host-level evidence first. If a different code appears, that is a moved boundary, not automatic success.
Preserve whether the result came from filtering, catalog storage, administration, or query enumeration; those paths can share a catalog name while requiring different corrective actions.
Correction and acceptance criteria
Correction: Use a supported code page or the Unicode query interface and keep byte encoding consistent with the declaration. 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 non-ASCII terms round-trip correctly and deliberately unsupported identifiers fail before query parsing. 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.