| Previous | Next |
| QPARSE_E_EXPECTING_COMMA | QPARSE_E_WEIGHT_OUT_OF_RANGE |
QPARSE_E_UNEXPECTED_EOS
Input ended before the query construct was complete
QPARSE_E_UNEXPECTED_EOS is HRESULT 0x80041672. Windows documents it as “Unexpected end of string.”
Interpretation
This result belongs to legacy Windows query parsing and is returned while reaching physical string end with an outstanding parser expectation. The exact condition is: a dangling operator, open delimiter, missing value or truncation leaves syntax incomplete.
Concrete sources
Observability checklist
- Record last complete token before releasing the relevant objects.
- Associate expected token with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for original length under the same provider or handler version.
- Record the source and normalization path of transmitted length, not only its display form.
- Record final parser input bytes before releasing the relevant objects.
Investigation order
- Capture last complete token and expected token at the call boundary that returns this result.
- Confirm the operation reached reaching physical string end with an outstanding parser expectation with the intended original length.
- compare original and transmitted lengths and record the exact expected token at EOS.
Corrective action
Restore the specific missing node or fix string-length/encoding transport. Retrying identical parser bytes cannot succeed; regenerate the specific token or schema pairing that failed.
What must not be inferred
Neighboring status codes
QPARSE_E_EXPECTING_EOS finds extra input after a complete expression.
Developer and administrator guidance
Reproduction example
An embedded null truncates text after System.Title =. Correct length handling restores the intended literal.
Official Microsoft references
Looking for a different code? Search another status or error code.