| Previous | Next |
| QPLIST_E_BAD_GUID | QPLIST_E_CANT_SET_PROPERTY |
QPLIST_E_EXPECTING_PROP_SPEC
A complete property specifier is missing
QPLIST_E_EXPECTING_PROP_SPEC is HRESULT 0x8004165A. Windows documents it as “Expecting property specifier.”
Exact contract boundary
This result belongs to legacy Windows property-list parsing and is returned while assembling the namespace GUID and property identifier that select one indexed property. The exact condition is: the entry supplies only part of the identity, contains an empty field or uses unsupported shorthand.
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.
Input or state defects
Rejection of the property list does not yet distinguish file access, tokenization, type composition, GUID syntax or duplicate-definition failure.
Incident record
- Compare failing and known-good values for property-set GUID under the same provider or handler version.
- Record the source and normalization path of property ID, not only its display form.
- Record delimiter sequence before releasing the relevant objects.
- Associate known-good specification with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for property-list file identity and hash under the same provider or handler version.
Hash the complete file if it is sensitive while retaining encoding, line, column, raw token class and the surrounding property declaration.
How to isolate the cause
- Capture property-set GUID and property ID at the call boundary that returns this result.
- Confirm the operation reached assembling the namespace GUID and property identifier that select one indexed property with the intended parsed name and type.
- validate the GUID-property-ID pair as one unit and check whether an earlier token shifted parser state.
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.
Restoration strategy
Reconstruct the full specifier from schema metadata and parse the entire file again. Delay cannot repair a deterministic file, token or type-grammar defect; retry only after the property list or its readable source changes.
Scope of the result
It does not prove that every property definition is unusable or that reindexing is required; it identifies a property-list read or grammar boundary.
Comparison with adjacent codes
QPLIST_E_EXPECTING_NAME waits for the display/query name rather than structured identity.
Developer and administrator guidance
Example from a search pipeline
A generator emits the format GUID but omits the property ID. The complete schema pair restores deterministic lookup.
Official Microsoft references
Looking for a different code? Search another status or error code.