| Previous | Next |
| QPLIST_E_EXPECTING_TYPE | QPLIST_E_EXPECTING_INTEGER |
QPLIST_E_UNRECOGNIZED_TYPE
The supplied property type token is not recognized
QPLIST_E_UNRECOGNIZED_TYPE is the failure HRESULT 0x80041655 (-2147215787 signed; 2147751509 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1655. AllStat describes it as “Unrecognized type.”
Legacy API stage
This result belongs to legacy Windows property-list parsing and is returned while mapping a present textual type to the legacy OLE DB type set. The exact condition is: a misspelling, modern provider type, hidden character, unsupported numeric form or malformed modifier reaches the parser. 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.
Why it appears
- an incomplete exact type token hides the distinction needed to separate this HRESULT from a later catalog or service failure.
- changes in byte representation between validation and execution can reproduce the result even when the user-visible input looks unchanged.
- Retrying this result with the same base type leaves the decisive contract violation intact.
- This result can appear when VECTOR/BYREF modifiers disagrees with the state expected while mapping a present textual type to the legacy OLE DB type set.
- a stale or transformed parser version can make the component observe that a misspelling, modern provider type, hidden character, unsupported numeric form or malformed modifier reaches the parser.
The strongest hypothesis for this HRESULT must account for the operation—mapping a present textual type to the legacy OLE DB type set—and the documented condition. Rejection of the property list does not yet distinguish file access, tokenization, type composition, GUID syntax or duplicate-definition failure.
Developer evidence
- compare failing and known-good values for exact type token under the same provider or handler version.
- record the source and normalization path of byte representation, not only its display form.
- use base type to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
- preserve VECTOR/BYREF modifiers before objects or work items are released.
- associate parser version 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.
Disciplined troubleshooting
- Capture exact type token and byte representation at the call boundary that returns this result.
- confirm the operation reached mapping a present textual type to the legacy OLE DB type set with the intended base type.
- perform the decisive check: preserve the exact token and compare it with the supported SDK DBTYPE representation.
- reduce the case until changing VECTOR/BYREF modifiers alone changes the HRESULT or proves it irrelevant.
- apply the recovery only after verifying parser 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.
Retry conditions
Replace it with the correct supported type without coercing the property merely to pass parsing. 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.
Misleading assumptions
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.
Related query outcomes
QPLIST_E_EXPECTING_TYPE means no type token was supplied. 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.
Concrete troubleshooting case
A configuration emits the language type `string`; the legacy parser requires an OLE DB DBTYPE token. The serializer becomes provider-aware. 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.