| Previous | Next |
| FILTER_S_DISK_FULL | FILTER_S_NO_SECURITY_DESCRIPTOR |
FILTER_S_NO_PROPSETS
Document contains no property sets
FILTER_S_NO_PROPSETS is HRESULT 268090 (0x0004173A) from Indexing Service. AllStat describes it as “The document has no property sets.” The severity bit indicates a nonfailure result, but the value carries a specific condition that must not be collapsed into plain S_OK.
In the legacy Indexing Service or IFilter pipeline, this result means that the document has no property sets. Ordinary completion must not be inferred from it until the owning component’s state and outputs agree.
Where the status is encountered
- Legacy Indexing Service catalog processing; log the exact method and object state instead of interpreting the constant outside that contract.
- IFilter text and property extraction; log the exact method and object state instead of interpreting the constant outside that contract.
- Search enumeration, scan scheduling, or catalog administration; log the exact method and object state instead of interpreting the constant outside that contract.
Because it is informational, a language binding may expose it as success and hide the symbolic distinction. Keep the original HRESULT available until the code-specific branch has run.
What must be true before accepting it
Verify that the absence of property sets is valid for the format and text extraction can proceed independently. Only this contract check establishes that it is safe for the caller’s next step.
The return of it can follow observable side effects, so recovery begins with state reconciliation.
Evidence and telemetry
- preserve document format and filter CLSID.
- preserve property-set enumeration result.
- preserve text chunk availability.
- preserve file-system metadata.
- preserve expected versus optional property schema.
Also record filter_s_no_propsets_operation, filter_s_no_propsets_state_before, filter_s_no_propsets_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. For privacy-safe it diagnostics, log metadata and fingerprints instead of confidential source values.
Difference from nearby results
It must be distinguished from ordinary S_OK and from failure-severity values in the same API family; its documented state changes control the next action.
A nearby HRESULT can change object ownership, output validity, or the permitted next method.
Correct handling and recovery
Continue with text or other available metadata. Do not synthesize property values; record format support if the document was expected to contain structured properties.
Retry it only when a documented input or state has changed. Before another call following it, confirm that completed side effects are idempotent or reconciled.
Practical scenario
A plain-text file has no OLE property sets. The indexer stores content and file-system metadata while leaving document-summary fields absent.
A regression test should reproduce it, assert the relevant outputs and state, then change only the decisive condition and verify the expected neighboring result or ordinary completion.
References
- Microsoft: Filter interface values — official Microsoft material used to interpret it.
- Microsoft: About Indexing Service filters
- Microsoft: Using custom filters
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.