| Previous | Next |
| QPLIST_E_EXPECTING_NAME | QPLIST_E_UNRECOGNIZED_TYPE |
QPLIST_E_EXPECTING_TYPE
A property definition is missing its type specifier
QPLIST_E_EXPECTING_TYPE is the failure HRESULT 0x80041654 (-2147215788 signed; 2147751508 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1654. AllStat describes it as “Expecting type specifier.”
Exact contract boundary
This result belongs to legacy Windows property-list parsing and is returned while reading the type field after a property identity has been accepted. The exact condition is: the entry ends, contains an empty field or substitutes a display format where an OLE DB DBTYPE is required. 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
- a stale or transformed property identity can make the component observe that the entry ends, contains an empty field or substitutes a display format where an OLE DB DBTYPE is required.
- an incomplete raw type field hides the distinction needed to separate this HRESULT from a later catalog or service failure.
- changes in expected DBTYPE between validation and execution can reproduce the result even when the user-visible input looks unchanged.
- Retrying this result with the same delimiter sequence leaves the decisive contract violation intact.
- This result can appear when schema version disagrees with the state expected while reading the type field after a property identity has been accepted.
The strongest hypothesis for this HRESULT must account for the operation—reading the type field after a property identity has been accepted—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
- associate property identity with the exact UTC timestamp and correlation identifier.
- compare failing and known-good values for raw type field under the same provider or handler version.
- record the source and normalization path of expected DBTYPE, not only its display form.
- use delimiter sequence to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
- preserve schema version before objects or work items are released.
- associate property-list file identity and hash with the exact UTC timestamp and correlation identifier.
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 identity and raw type field at the call boundary that returns this result.
- confirm the operation reached reading the type field after a property identity has been accepted with the intended expected DBTYPE.
- perform the decisive check: compare the current property with authoritative schema metadata and the exact delimiter sequence.
- reduce the case until changing delimiter sequence alone changes the HRESULT or proves it irrelevant.
- apply the recovery only after verifying schema version; 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
Emit a supported base DBTYPE and keep VECTOR/BYREF modifiers separate. 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_UNRECOGNIZED_TYPE means a token exists but cannot be mapped. 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 custom property name is present but its type column is blank. The generator derives DBTYPE_WSTR from schema instead of guessing. 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.