| Previous | Next |
| QUERY_E_ALLNOISE | QUERY_E_TIMEDOUT |
QUERY_E_TOOCOMPLEX
The query plan exceeds the engine complexity limit
QUERY_E_TOOCOMPLEX is HRESULT 0x80041606. Windows documents it as “The query was too complex to be executed.”
Contract and failing stage
This result belongs to legacy Windows query execution and is returned while expanding and planning Boolean branches, terms, scopes, ranges, ranking and groups. The exact condition is: valid-looking syntax that becomes too large or deeply nested for the legacy planner.
Conditions that produce it
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.
Evidence to preserve
- Associate Boolean-node count with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for expanded term count under the same provider or handler version.
- Record the source and normalization path of scope count, not only its display form.
- Record smallest removed branch that changes the HRESULT before releasing the relevant objects.
- Associate provider command text and dialect with the exact UTC timestamp and correlation identifier.
Redact private literals if necessary, but keep clause boundaries, canonical properties, parameter types, dialect and parser or provider offsets.
Diagnostic sequence
- Capture Boolean-node count and expanded term count at the call boundary that returns this result.
- Confirm the operation reached expanding and planning Boolean branches, terms, scopes, ranges, ranking and groups with the intended scope count.
- count logical nodes and reduce OR lists, wildcard expansion, nested groups and generated access filters independently.
Begin with a known-good minimal command against the same catalog and restore projection, restriction, sorting, grouping and scope one component at a time.
Recovery and retry
Simplify, deduplicate or split the request while preserving ranking and access semantics. Backoff helps only with measured transient load or timeout; it cannot repair invalid clauses, projection metadata, scopes or command state.
What the code does not prove
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.
Related HRESULT values
QUERY_E_TIMEDOUT means an accepted plan ran too long; this value identifies excessive plan complexity.
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.
Practical scenario
Thousands of allowed directories become one OR chain. Binary reduction finds scope expansion as the key factor, and the product batches scopes.
Official Microsoft references
Looking for a different code? Search another status or error code.