| 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 the failure HRESULT 0x8004165A (-2147215782 signed; 2147751514 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x165A. AllStat describes 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 stage matters because converting the result to a generic COM failure removes the information needed to choose the owner and retry policy.
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
- an incomplete property-set GUID hides the distinction needed to separate this HRESULT from a later catalog or service failure.
- changes in property ID between validation and execution can reproduce the result even when the user-visible input looks unchanged.
- Retrying this result with the same parsed name and type leaves the decisive contract violation intact.
- This result can appear when delimiter sequence disagrees with the state expected while assembling the namespace GUID and property identifier that select one indexed property.
- a stale or transformed known-good specification can make the component observe that the entry supplies only part of the identity, contains an empty field or uses unsupported shorthand.
The strongest hypothesis for this HRESULT must account for the operation—assembling the namespace GUID and property identifier that select one indexed property—and the documented condition. 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.
- use parsed name and type to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
- preserve delimiter sequence before objects or work items are released.
- 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.
Evidence for this HRESULT should reflect what the component actually received. 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.
- perform the decisive check: validate the GUID-property-ID pair as one unit and check whether an earlier token shifted parser state.
- reduce the case until changing delimiter sequence alone changes the HRESULT or proves it irrelevant.
- apply the recovery only after verifying known-good specification; preserve the original result for comparison.
A useful control for this HRESULT changes one dimension at a time. 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. Retry it only after the responsible input or state changes and the previous operation has completed or been cancelled. 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. Without code-specific evidence for this HRESULT, the value also cannot identify which wrapper, configuration, handler or service transition introduced the condition.
Comparison with adjacent codes
QPLIST_E_EXPECTING_NAME waits for the display/query name rather than structured identity. Keep the symbolic HRESULT beside the stage name in telemetry because nearby constants may require different owners, user messages and retry rules despite the same visible symptom.
Developer and administrator guidance
Retain the property-list file hash, encoding, parser version, line and column, raw token and expected grammar production. Do not log credentials or unrestricted document content. Before replacing the whole property configuration for this HRESULT, validate a copied file and preserve the exact failing location.
Example from a search pipeline
A generator emits the format GUID but omits the property ID. The complete schema pair restores deterministic lookup. A regression test for this HRESULT should assert the decisive evidence, change only the responsible condition, and include one neighboring HRESULT so future code cannot collapse distinct failures into a generic message.
Official Microsoft references
- Microsoft: legacy Indexing Service error messages
- Microsoft: OLE DB provider for Indexing Service
- Microsoft: Windows Search SQL syntax
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.