What does HRESULT 0x8004165B (QPLIST_E_CANT_SET_PROPERTY) mean?

 
Previous Next
QPLIST_E_EXPECTING_PROP_SPEC QPLIST_E_DUPLICATE

QPLIST_E_CANT_SET_PROPERTY

The parsed property mapping could not be stored

QPLIST_E_CANT_SET_PROPERTY is the failure HRESULT 0x8004165B (-2147215781 signed; 2147751515 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x165B. AllStat describes it as “Failed to set property name.”

Legacy API stage

This result belongs to legacy Windows property-list parsing and is returned while committing a recognized name, identity and type into the query property-list object. The exact condition is: a name collision, identity/type mismatch, invalid parser state, allocation failure or provider constraint prevents registration. 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

  • changes in property name between validation and execution can reproduce the result even when the user-visible input looks unchanged.
  • Retrying this result with the same canonical identity leaves the decisive contract violation intact.
  • This result can appear when DBTYPE disagrees with the state expected while committing a recognized name, identity and type into the query property-list object.
  • a stale or transformed entry ordinal can make the component observe that a name collision, identity/type mismatch, invalid parser state, allocation failure or provider constraint prevents registration.
  • an incomplete provider error records hides the distinction needed to separate this HRESULT from a later catalog or service failure.

The strongest hypothesis for this HRESULT must account for the operation—committing a recognized name, identity and type into the query property-list object—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

  • record the source and normalization path of property name, not only its display form.
  • use canonical identity to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
  • preserve DBTYPE before objects or work items are released.
  • associate entry ordinal with the exact UTC timestamp and correlation identifier.
  • compare failing and known-good values for provider error records under the same provider or handler version.
  • record the source and normalization path of property-list file identity and hash, not only its display form.

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

  1. Capture property name and canonical identity at the call boundary that returns this result.
  2. confirm the operation reached committing a recognized name, identity and type into the query property-list object with the intended DBTYPE.
  3. perform the decisive check: test the definition alone and compare all earlier mappings with the same name or property identity.
  4. reduce the case until changing entry ordinal alone changes the HRESULT or proves it irrelevant.
  5. apply the recovery only after verifying provider error records; 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

Resolve the mapping conflict or invalid metadata; preserve a one-entry reproducer if a valid definition still fails. 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_DUPLICATE explicitly proves a repeated property name; it is broader. 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 custom alias collides with a built-in name mapped to another GUID. Isolating the entry reveals the semantic conflict. 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

Looking for a different code? Search another status or error code.