What does HRESULT 0x8004166C (QPARSE_E_EXPECTING_REGEX) mean?

 
Previous Next
QPARSE_E_UNSUPPORTED_PROPERTY_TYPE QPARSE_E_EXPECTING_REGEX_PROPERTY

QPARSE_E_EXPECTING_REGEX

The parser expected a regular-expression operand

QPARSE_E_EXPECTING_REGEX is the failure HRESULT 0x8004166C (-2147215764 signed; 2147751532 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x166C. AllStat describes it as “Expecting regular expression.”

Interpretation

This result belongs to legacy Windows query parsing and is returned while reading the pattern side of a regex construct. The exact condition is: the pattern is empty, lost through escaping or replaced by a delimiter/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

  • Retrying this result with the same user pattern leaves the decisive contract violation intact.
  • This result can appear when escaped token disagrees with the state expected while reading the pattern side of a regex construct.
  • a stale or transformed delimiter form can make the component observe that the pattern is empty, lost through escaping or replaced by a delimiter/operator.
  • an incomplete parser offset hides the distinction needed to separate this HRESULT from a later catalog or service failure.
  • changes in owning property between validation and execution can reproduce the result even when the user-visible input looks unchanged.

The strongest hypothesis for this HRESULT must account for the operation—reading the pattern side of a regex construct—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

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

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 user pattern and escaped token at the call boundary that returns this result.
  2. confirm the operation reached reading the pattern side of a regex construct with the intended delimiter form.
  3. perform the decisive check: capture user pattern, language-string representation and final query token separately.
  4. reduce the case until changing parser offset alone changes the HRESULT or proves it irrelevant.
  5. apply the recovery only after verifying owning property; 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

Provide a nonempty valid pattern; never substitute `.*` silently. 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_EXPECTING_REGEX_PROPERTY concerns the property target, not the pattern. 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

Multiple escaping layers remove the only pattern character. Logging final parser input reveals the empty operand. 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.