| Previous | Next |
| QPLIST_E_VECTORBYREF_USED_ALONE | QPARSE_E_UNEXPECTED_NOT |
QPLIST_E_BYREF_USED_WITHOUT_PTRTYPE
DBTYPE_BYREF is paired with an unsupported base type
QPLIST_E_BYREF_USED_WITHOUT_PTRTYPE is the failure HRESULT 0x8004165E (-2147215778 signed; 2147751518 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x165E. AllStat describes it as “DBTYPE_BYREF must be used with DBTYPE_STR, DBTYPE_WSTR, DBTYPE_GUID or DBTYPE_UI1 types.”
Operation and state
This result belongs to legacy Windows property-list parsing and is returned while checking whether a by-reference type uses a pointer-compatible base DBTYPE. The exact condition is: BYREF is applied to a numeric/date type, a string is misclassified, or flags are combined incorrectly. 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.
Failure paths to examine
- a stale or transformed complete flag value can make the component observe that BYREF is applied to a numeric/date type, a string is misclassified, or flags are combined incorrectly.
- an incomplete base DBTYPE hides the distinction needed to separate this HRESULT from a later catalog or service failure.
- changes in property schema between validation and execution can reproduce the result even when the user-visible input looks unchanged.
- Retrying this result with the same accessor binding leaves the decisive contract violation intact.
- This result can appear when BYREF selection rule disagrees with the state expected while checking whether a by-reference type uses a pointer-compatible base DBTYPE.
The strongest hypothesis for this HRESULT must account for the operation—checking whether a by-reference type uses a pointer-compatible base DBTYPE—and the documented condition. Rejection of the property list does not yet distinguish file access, tokenization, type composition, GUID syntax or duplicate-definition failure.
Data to collect first
- associate complete flag value with the exact UTC timestamp and correlation identifier.
- compare failing and known-good values for base DBTYPE under the same provider or handler version.
- record the source and normalization path of property schema, not only its display form.
- use accessor binding to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
- preserve BYREF selection rule 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.
Step-by-step diagnosis
- Capture complete flag value and base DBTYPE at the call boundary that returns this result.
- confirm the operation reached checking whether a by-reference type uses a pointer-compatible base DBTYPE with the intended property schema.
- perform the decisive check: inspect the exact base type and the generator rule that selected by-reference transfer.
- reduce the case until changing accessor binding alone changes the HRESULT or proves it irrelevant.
- apply the recovery only after verifying BYREF selection rule; 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.
Continuation policy
Use BYREF only with the pointer-compatible types named by the SDK contract or bind the value normally. 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.
Limits of this HRESULT
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.
Distinguishing similar results
QPLIST_E_VECTORBYREF_USED_ALONE means the base type is missing entirely. 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.
Operational case
A converter marks DBTYPE_I4 as BYREF to avoid copying. The parser rejects it, and the accessor returns to a normal integer binding. 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.