| Previous | Next |
| WBREAK_E_END_OF_TEXT | WBREAK_E_BUFFER_TOO_SMALL |
WBREAK_E_QUERY_ONLY
The requested word-breaker feature is restricted to query mode
WBREAK_E_QUERY_ONLY is HRESULT 0x80041782 (-2147215486 signed; 2147751810 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF for these values), and code field is 0x1782. Standard HRESULT severity rules classify the value as a failure. AllStat describes the value as “Feature only available in query mode.”
Interpretation in context
This result belongs to invoking a query-expansion operation while the breaker is configured for index-time processing. The decisive interpretation is that the API feature depends on query semantics that are not available in indexing mode. Keep the symbolic constant and method stage together in logs; its hexadecimal value alone cannot identify the owning transition or input.
Word breakers process TEXT_SOURCE buffers and report words or phrases through sinks. In the result investigation, locale, mode, refill behavior and component registration must be captured together. This context narrows the responsible component without replacing the code-specific checks below.
Conditions to test
- This result: Query-only phrase expansion is called during indexing.
- This result: Mode flags are copied from the wrong pipeline.
- This result: One breaker instance is shared between index and query tasks.
The useful hypothesis for it must explain both invoking a query-expansion operation while the breaker is configured for index-time processing and the documented condition. Compare the failing case with a control that preserves requested breaker method or option and changes only mode used at initialization; this prevents unrelated environment differences from dominating the result test.
Incident record
- check requested breaker method or option.
- check mode used at initialization.
- check caller pipeline role.
- check instance ownership and thread.
Capture requested breaker method or option before releasing objects, closing handles or reconnecting. Retain the raw HRESULT with mode used at initialization, component version, UTC timestamp and correlation ID. Bound the result telemetry to diagnostic metadata because document content, credentials and unrestricted query text may be sensitive.
Step-by-step diagnosis
- Identify the exact feature that requires query mode. Associate this observation specifically with it.
- Trace initialization flags for the same breaker instance. Associate this observation specifically with it.
- Separate index-time token emission from query-time expansion. Associate this observation specifically with it.
- Create independent instances for concurrent modes. Associate this observation specifically with it.
Change one variable per it control run. Preserve the component version and target identity, then alter only the condition described as the API feature depends on query semantics that are not available in indexing mode. This isolates whether it is causal rather than merely repeatable.
Retry decision
Move the operation to query processing or initialize the appropriate query-mode object. Repeating it in index mode cannot succeed. Record whether invoking a query-expansion operation while the breaker is configured for index-time processing produced any content, update or state transition before returning. If completion remains unknown, the path must not replay non-idempotent work until the owner confirms final state.
The retry gate for it should be a concrete change in requested breaker method or option or mode used at initialization. A timer alone cannot demonstrate that the result contract condition has changed.
What the value cannot establish
It does not mean the input text or language is invalid. Without the call boundary for invoking a query-expansion operation while the breaker is configured for index-time processing, it also cannot identify which wrapper or configuration layer introduced the condition.
Adjacent contract states
PSINK_E_QUERY_ONLY is reported by phrase-sink behavior; this HRESULT belongs to the word-breaker feature itself. In it telemetry, preserve neighboring constants separately because the same visible symptom may require a different caller action, owner or recovery gate.
Developer and administrator actions
- At the code boundary, keep requested breaker method or option beside the returned HRESULT; preserve the observation under the result correlation record.
- In telemetry, correlate mode used at initialization with the target and component generation; preserve the observation under the result correlation record.
- For regression coverage, force the documented condition: the API feature depends on query semantics that are not available in indexing mode; preserve the observation under the result correlation record.
- For operations staff, expose the corrective state change rather than a generic retry button; preserve the observation under the result correlation record.
- After remediation, validate one known-good control and the original failing case; preserve the observation under the result correlation record.
Concrete scenario
An indexing path accidentally enables a query-time alternative-word option. Mode-specific construction removes the invalid call. In this scenario, handling it at its real contract boundary prevents the application from collapsing a precise state into an unhelpful generic “search failed” message.
Official Microsoft references
- Microsoft: Word-Breaking values — official contract information relevant to it.
- Microsoft: IWordBreaker interface
- Microsoft: IWordBreaker::BreakText
- Microsoft: Windows Search language resources
- Microsoft: TEXT_SOURCE structure
Looking for a different code? Search another status or error code.