What does HRESULT 0x80041656 (QPLIST_E_EXPECTING_INTEGER) mean?

 
Previous Next
QPLIST_E_UNRECOGNIZED_TYPE QPLIST_E_EXPECTING_CLOSE_PAREN

QPLIST_E_EXPECTING_INTEGER

The property-list grammar requires an integer field

QPLIST_E_EXPECTING_INTEGER is the failure HRESULT 0x80041656 (-2147215786 signed; 2147751510 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF), and code is 0x1656. AllStat describes it as “Expecting integer.”

Contract and failing stage

This result belongs to legacy Windows property-list parsing and is returned while reading a numeric property-specification component or option. The exact condition is: an empty field, symbolic label, localized grouping separator or unsupported notation appears where digits are 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.

Conditions that produce it

  • changes in grammar field between validation and execution can reproduce the result even when the user-visible input looks unchanged.
  • Retrying this result with the same raw numeric token leaves the decisive contract violation intact.
  • This result can appear when allowed range disagrees with the state expected while reading a numeric property-specification component or option.
  • a stale or transformed surrounding delimiters can make the component observe that an empty field, symbolic label, localized grouping separator or unsupported notation appears where digits are required.
  • an incomplete formatter locale 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—reading a numeric property-specification component or option—and the documented condition. Rejection of the property list does not yet distinguish file access, tokenization, type composition, GUID syntax or duplicate-definition failure.

Evidence to preserve

  • record the source and normalization path of grammar field, not only its display form.
  • use raw numeric token to test whether the failure belongs to parsing, execution, indexing or capability negotiation.
  • preserve allowed range before objects or work items are released.
  • associate surrounding delimiters with the exact UTC timestamp and correlation identifier.
  • compare failing and known-good values for formatter locale 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.

Diagnostic sequence

  1. Capture grammar field and raw numeric token at the call boundary that returns this result.
  2. confirm the operation reached reading a numeric property-specification component or option with the intended allowed range.
  3. perform the decisive check: identify the grammar owner of the number and preserve the unformatted application value.
  4. reduce the case until changing surrounding delimiters alone changes the HRESULT or proves it irrelevant.
  5. apply the recovery only after verifying formatter locale; 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.

Recovery and retry

Emit an invariant integer in the permitted range; never substitute zero unless zero is semantically valid. 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.

What the code does not prove

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 HRESULT values

QPARSE_E_EXPECTING_INTEGER concerns query text, not property-list configuration. 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.

Practical scenario

A formatter emits `1,033` for a property identifier. The comma terminates the token, so invariant numeric formatting is introduced. 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.