| Previous | Next |
| QUERY_E_INVALIDQUERY | QUERY_E_INVALIDSORT |
QUERY_E_INVALIDRESTRICTION
The restriction expression could not be parsed
QUERY_E_INVALIDRESTRICTION is HRESULT 0x80041602. Windows documents it as “The query restriction could not be parsed.”
Operation and state
This result belongs to legacy Windows query execution and is returned while parsing the predicate that limits catalog rows, including property comparisons and full-text conditions. The exact condition is: a WHERE/restriction grammar or type-pairing defect, not an empty-result condition.
Failure paths to examine
A failed command or empty rowset is only the visible symptom; it does not identify which restriction, projection, sort, scope, timeout or catalog state violated the query contract.
Data to collect first
- Compare failing and known-good values for final restriction text under the same provider or handler version.
- Record the source and normalization path of parser offset, not only its display form.
- Record literal type and locale before releasing the relevant objects.
- Associate clause-by-clause reproducer with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for provider command text and dialect under the same provider or handler version.
Redact private literals if necessary, but keep clause boundaries, canonical properties, parameter types, dialect and parser or provider offsets.
Step-by-step diagnosis
- Capture final restriction text and parser offset at the call boundary that returns this result.
- Confirm the operation reached parsing the predicate that limits catalog rows, including property comparisons and full-text conditions with the intended property schema.
- reduce the predicate until the exact operator, property, literal or delimiter that breaks parsing is isolated.
Begin with a known-good minimal command against the same catalog and restore projection, restriction, sorting, grouping and scope one component at a time.
Continuation policy
Correct escaping, property type, operator or grouping and then rebuild the restriction structurally. Backoff helps only with measured transient load or timeout; it cannot repair invalid clauses, projection metadata, scopes or command state.
Limits of this HRESULT
It does not by itself prove catalog corruption, service outage, access denial or absence of matches; the query stage and provider records must identify the failing clause or state.
Distinguishing similar results
QPARSE_E_INVALID_QUERY and token-specific QPARSE values can expose a more precise parser defect.
Developer and administrator guidance
Retain final command text, dialect, catalog generation, parameter values, timeout, cancellation state and chained OLE DB error records. Before rebuilding the catalog or restarting the provider, reproduce the minimal command and preserve its chained errors.
Operational case
An unescaped quote enters a title predicate. Removing WHERE proves the projection works; restoring branches identifies the exact malformed clause.
Official Microsoft references
Looking for a different code? Search another status or error code.