| Previous | Next |
| QPARSE_E_EXPECTING_CURRENCY | QPARSE_E_EXPECTING_BRACE |
QPARSE_E_EXPECTING_GUID
The parser expected a GUID literal
QPARSE_E_EXPECTING_GUID is HRESULT 0x80041665. Windows documents it as “Expecting GUID.”
Operation and state
This result belongs to legacy Windows query parsing and is returned while reading a GUID-valued comparison or object identifier. The exact condition is: the field is empty, uses a friendly name, has bad braces/hyphens or is truncated.
Failure paths to examine
Data to collect first
- Compare failing and known-good values for raw GUID under the same provider or handler version.
- Record the source and normalization path of byte length, not only its display form.
- Record first invalid offset before releasing the relevant objects.
- Associate intended identifier 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.
Step-by-step diagnosis
- Capture raw GUID and byte length at the call boundary that returns this result.
- Confirm the operation reached reading a GUID-valued comparison or object identifier with the intended brace form.
- capture raw bytes and compare with the intended semantic identifier.
Continuation policy
Emit a canonical GUID and verify both syntax and meaning. Retrying identical parser bytes cannot succeed; regenerate the specific token or schema pairing that failed.
Limits of this HRESULT
Distinguishing similar results
QPARSE_E_INVALID_LITERAL covers a present typed literal that remains invalid.
Developer and administrator guidance
Operational case
A template truncates the final GUID field. Strict round-trip parsing detects the defect before execution.
Official Microsoft references
Looking for a different code? Search another status or error code.