| Previous | Next |
| QPLIST_E_EXPECTING_INTEGER | QPLIST_E_EXPECTING_GUID |
QPLIST_E_EXPECTING_CLOSE_PAREN
A property-list construct lacks its closing parenthesis
QPLIST_E_EXPECTING_CLOSE_PAREN is HRESULT 0x80041657. Windows documents it as “Expecting closing parenthesis.”
Where the failure belongs
This result belongs to legacy Windows property-list parsing and is returned while finishing a parenthesized type or property specification. The exact condition is: conditional generation, nested groups, quoting or a malformed previous entry leaves the opening parenthesis unmatched.
This value belongs to the legacy property-list parser used to describe indexed properties and their types. Diagnose the external list as structured configuration: preserve line, column, token, type grammar and the property-list version instead of treating the file as arbitrary text. The exact public message comes from the legacy SDK contract; current property-system documentation does not replace the property-list grammar that rejected this file.
Likely causes
Rejection of the property list does not yet distinguish file access, tokenization, type composition, GUID syntax or duplicate-definition failure.
Telemetry that matters
- Record parenthesis stack before releasing the relevant objects.
- Associate quote state with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for previous entry terminator under the same provider or handler version.
- Record the source and normalization path of generator branch, not only its display form.
Hash the complete file if it is sensitive while retaining encoding, line, column, raw token class and the surrounding property declaration.
Verification workflow
- Capture opening-token position and parenthesis stack at the call boundary that returns this result.
- Confirm the operation reached finishing a parenthesized type or property specification with the intended quote state.
- use quote-aware balance tracing from the start of the entry and identify the branch that emitted the opening token.
Begin with a one-property list accepted by the same parser, then restore the failing declaration token by token while preserving encoding and line endings.
Safe remediation
Regenerate the complete balanced entry instead of appending a blind final parenthesis. Delay cannot repair a deterministic file, token or type-grammar defect; retry only after the property list or its readable source changes.
Avoid the wrong conclusion
It does not prove that every property definition is unusable or that reindexing is required; it identifies a property-list read or grammar boundary.
How nearby codes differ
QPARSE_E_EXPECTING_PAREN is the analogous query-text failure.
Developer and administrator guidance
Worked example
An optional flag branch emits (DBTYPE_WSTR but owns no closing token. Making the syntax node own both delimiters fixes every variant.
Official Microsoft references
Looking for a different code? Search another status or error code.