| Previous | Next |
| QUERY_E_DUPLICATE_RANGE_NAME | QPLIST_E_READ_ERROR |
QPLIST_E_CANT_OPEN_FILE
The property-list file cannot be opened
QPLIST_E_CANT_OPEN_FILE is HRESULT 0x80041651. Windows documents it as “Can not open file.”
Where the failure belongs
This result belongs to legacy Windows property-list parsing and is returned while opening the external query-property definition before parsing begins. The exact condition is: the configured file is missing, resolves under a different service directory, or is unreadable by the service identity.
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.
Likely causes
Rejection of the property list does not yet distinguish file access, tokenization, type composition, GUID syntax or duplicate-definition failure.
Telemetry that matters
- Record the source and normalization path of resolved path, not only its display form.
- Record file attributes and owner before releasing the relevant objects.
- Associate working directory and expansions with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for known-good file hash 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.
Hash the complete file if it is sensitive while retaining encoding, line, column, raw token class and the surrounding property declaration.
Verification workflow
- Capture resolved path and service identity at the call boundary that returns this result.
- Confirm the operation reached opening the external query-property definition before parsing begins with the intended file attributes and owner.
- resolve the path in the actual process context and prove a minimal read succeeds.
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.
Safe remediation
Restore a trusted readable file or correct the path/ACL without granting broad write access. Delay cannot repair a deterministic file, token or type-grammar defect; retry only after the property list or its readable source changes.
Avoid the wrong conclusion
It does not prove that every property definition is unusable or that reindexing is required; it identifies a property-list read or grammar boundary.
How nearby codes differ
QPLIST_E_READ_ERROR occurs after the file was opened and input failed later.
Developer and administrator guidance
Worked example
A relative path works in an administrator shell but resolves elsewhere for the service. Logging the full resolved path identifies the deployment defect.
Official Microsoft references
Looking for a different code? Search another status or error code.