| Previous | Next |
| QPARSE_E_NO_SUCH_PROPERTY | QPARSE_E_EXPECTING_COMMA |
QPARSE_E_EXPECTING_EOS
The parser expected end of string
QPARSE_E_EXPECTING_EOS is HRESULT 0x80041670. Windows documents it as “Expecting end of string.”
Where the failure belongs
This result belongs to legacy Windows query parsing and is returned while finishing a valid top-level expression. The exact condition is: a second fragment, trailing comma, unsupported option or hidden token follows valid content.
Likely causes
Telemetry that matters
- Record the source and normalization path of first trailing token, not only its display form.
- Record suffix source before releasing the relevant objects.
- Associate control characters with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for query mode under the same provider or handler version.
- Record the source and normalization path of final parser input bytes, not only its display form.
Verification workflow
- Capture first trailing token and longest valid prefix at the call boundary that returns this result.
- Confirm the operation reached finishing a valid top-level expression with the intended suffix source.
- capture the first trailing token and longest prefix that parses successfully.
Safe remediation
Remove or correctly integrate the suffix; truncate only after proving it is unintended. Retrying identical parser bytes cannot succeed; regenerate the specific token or schema pairing that failed.
Avoid the wrong conclusion
How nearby codes differ
QPARSE_E_UNEXPECTED_EOS is the opposite: input ends while more syntax is required.
Developer and administrator guidance
Worked example
A builder concatenates two WHERE fragments. An AST merger inserts the intended Boolean node.
Official Microsoft references
Looking for a different code? Search another status or error code.