What does HRESULT 0x80041660 (QPARSE_E_UNEXPECTED_NOT) mean?

 
Previous Next
QPLIST_E_BYREF_USED_WITHOUT_PTRTYPE QPARSE_E_EXPECTING_INTEGER

QPARSE_E_UNEXPECTED_NOT

A NOT operator is in an invalid position

QPARSE_E_UNEXPECTED_NOT is the failure HRESULT 0x80041660 (-2147215776 signed; 2147751520 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1660. AllStat describes it as “Unexpected NOT operator.”

Interpretation

This result belongs to legacy Windows query parsing and is returned while building a Boolean restriction. The exact condition is: NOT has no valid operand or follows another operator. This stage matters because converting the result to a generic COM failure removes the information needed to choose the owner and retry policy.

This value comes from the legacy Indexing Service query parser. The exact final string, parser mode, locale and target property schema matter more than the query text shown in a user interface, because escaping and serialization can alter the token stream before parsing. Current Search SQL documentation can help compare operators and property syntax, but the failing token must still be interpreted under this legacy parser dialect.

Concrete sources

  • an incomplete previous token hides the distinction needed to separate this HRESULT from a later catalog or service failure.
  • changes in next token between validation and execution can reproduce the result even when the user-visible input looks unchanged.
  • Retrying this result with the same parenthesis depth leaves the decisive contract violation intact.
  • This result can appear when query form disagrees with the state expected while building a Boolean restriction.
  • a stale or transformed builder fragment can make the component observe that NOT has no valid operand or follows another operator.

The strongest hypothesis for this HRESULT must account for the operation—building a Boolean restriction—and the documented condition. A parse failure does not identify the expected token class, property type, locale conversion or escaping layer until the final parser input is preserved.

Observability checklist

  • compare failing and known-good values for previous token under the same provider or handler version.
  • record the source and normalization path of next token, not only its display form.
  • use parenthesis depth to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
  • preserve query form before objects or work items are released.
  • associate builder fragment with the exact UTC timestamp and correlation identifier.
  • compare failing and known-good values for final parser input bytes under the same provider or handler version.

Evidence for this HRESULT should reflect what the component actually received. Preserve a bounded token window, offsets, quote and delimiter state, locale and canonical property identity without logging unrelated query text.

Investigation order

  1. Capture previous token and next token at the call boundary that returns this result.
  2. confirm the operation reached building a Boolean restriction with the intended parenthesis depth.
  3. perform the decisive check: capture previous and next tokens plus grouping depth.
  4. reduce the case until changing query form alone changes the HRESULT or proves it irrelevant.
  5. apply the recovery only after verifying builder fragment; preserve the original result for comparison.

A useful control for this HRESULT changes one dimension at a time. Begin with a minimal expression using the same property and parser mode, then add the failing literal, operator or delimiter without changing locale or escaping.

Corrective action

Place negation only where the target grammar permits it. Retry it only after the responsible input or state changes and the previous operation has completed or been cancelled. Retrying identical parser bytes cannot succeed; regenerate the specific token or schema pairing that failed.

What must not be inferred

It does not prove that the user intent is invalid or that the catalog lacks data; it identifies how this parser interpreted the final serialized expression. Without code-specific evidence for this HRESULT, the value also cannot identify which wrapper, configuration, handler or service transition introduced the condition.

Neighboring status codes

QPARSE_E_UNEXPECTED_EOS is incomplete input; this value names the misplaced NOT. Keep the symbolic HRESULT beside the stage name in telemetry because nearby constants may require different owners, user messages and retry rules despite the same visible symptom.

Developer and administrator guidance

Retain final parser bytes, query form, token offset, expected token class, locale, escaping path and target property schema. Do not log credentials or unrestricted document content. Before changing catalog schema for this HRESULT, prove the final token stream and property type at the parser boundary.

Reproduction example

An optional exclusion value is empty and leaves `AND NOT`. Token validation removes the dangling operator. A regression test for this HRESULT should assert the decisive evidence, change only the responsible condition, and include one neighboring HRESULT so future code cannot collapse distinct failures into a generic message.

Official Microsoft references

Looking for a different code? Search another status or error code.