| Previous | Next |
| QPARSE_E_EXPECTING_PROPERTY | QPARSE_E_EXPECTING_PHRASE |
QPARSE_E_NOT_YET_IMPLEMENTED
The recognized query feature is not implemented
QPARSE_E_NOT_YET_IMPLEMENTED is HRESULT 0x80041669. Windows documents it as “Not yet implemented.”
Contract and failing stage
This result belongs to legacy Windows query parsing and is returned while translating a construct understood by this parser version only as an unsupported capability. The exact condition is: a newer or provider-specific feature reaches a legacy stub path.
Conditions that produce it
Evidence to preserve
- Associate smallest feature fragment with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for parser version under the same provider or handler version.
- Record the source and normalization path of dialect, not only its display form.
- Record supported equivalent before releasing the relevant objects.
- Associate final parser input bytes with the exact UTC timestamp and correlation identifier.
Diagnostic sequence
- Capture smallest feature fragment and parser version at the call boundary that returns this result.
- Confirm the operation reached translating a construct understood by this parser version only as an unsupported capability with the intended dialect.
- reduce the expression until one unsupported feature remains and record parser version/dialect.
Recovery and retry
Use a semantically faithful supported equivalent or reject the feature clearly. Retrying identical parser bytes cannot succeed; regenerate the specific token or schema pairing that failed.
What the code does not prove
Related HRESULT values
QPARSE_E_INVALID_QUERY says the expression is invalid; this value can identify a valid-looking unsupported feature.
Developer and administrator guidance
Practical scenario
A newer grouping option reaches a legacy provider. Capability detection selects a version-specific query plan.
Official Microsoft references
Looking for a different code? Search another status or error code.