| 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 HRESULT 0x80041655. Windows documents 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 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
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.
- Record VECTOR/BYREF modifiers before releasing the relevant objects.
- 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.
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.
- preserve the exact token and compare it with the supported SDK DBTYPE representation.
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. 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.
Related query outcomes
QPLIST_E_EXPECTING_TYPE means no type token was supplied.
Developer and administrator guidance
Concrete troubleshooting case
A configuration emits the language type string; the legacy parser requires an OLE DB DBTYPE token. The serializer becomes provider-aware.
Official Microsoft references
Looking for a different code? Search another status or error code.