| Previous | Next |
| QPLIST_E_READ_ERROR | QPLIST_E_EXPECTING_TYPE |
QPLIST_E_EXPECTING_NAME
A property name is missing at the current list position
QPLIST_E_EXPECTING_NAME is the failure HRESULT 0x80041653 (-2147215789 signed; 2147751507 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1653. AllStat describes it as “Expecting property name.”
Interpretation
This result belongs to legacy Windows property-list parsing and is returned while starting a property definition or reading the entry after a separator. The exact condition is: an empty generated field, end of file, misplaced type token or earlier malformed entry leaves no property name. 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.
Concrete sources
- This result can appear when line and column disagrees with the state expected while starting a property definition or reading the entry after a separator.
- a stale or transformed previous delimiter can make the component observe that an empty generated field, end of file, misplaced type token or earlier malformed entry leaves no property name.
- an incomplete next token hides the distinction needed to separate this HRESULT from a later catalog or service failure.
- changes in canonical-name source between validation and execution can reproduce the result even when the user-visible input looks unchanged.
- Retrying this result with the same file encoding leaves the decisive contract violation intact.
The strongest hypothesis for this HRESULT must account for the operation—starting a property definition or reading the entry after a separator—and the documented condition. Rejection of the property list does not yet distinguish file access, tokenization, type composition, GUID syntax or duplicate-definition failure.
Observability checklist
- preserve line and column before objects or work items are released.
- associate previous delimiter with the exact UTC timestamp and correlation identifier.
- compare failing and known-good values for next token under the same provider or handler version.
- record the source and normalization path of canonical-name source, not only its display form.
- use file encoding to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
- preserve property-list file identity and hash before objects or work items are released.
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.
Investigation order
- Capture line and column and previous delimiter at the call boundary that returns this result.
- confirm the operation reached starting a property definition or reading the entry after a separator with the intended next token.
- perform the decisive check: inspect the preceding delimiter, current token and generator field that should own the canonical name.
- reduce the case until changing canonical-name source alone changes the HRESULT or proves it irrelevant.
- apply the recovery only after verifying file encoding; 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.
Corrective action
Supply the intended canonical name and regenerate the entry from structured schema data. 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.
What must not be inferred
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.
Neighboring status codes
QPLIST_E_EXPECTING_PROP_SPEC waits for a structured property identity rather than the name token. 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.
Reproduction example
A generator emits a comma followed immediately by DBTYPE_WSTR because the name field is empty. Predeployment schema validation blocks it. 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.