| Previous | Next |
| FILTER_E_NO_SUCH_PROPERTY | FILTER_E_PARTIALLY_FILTERED |
FILTER_E_OFFLINE
The document is offline and its content is unavailable
FILTER_E_OFFLINE is HRESULT 0x8004173D (-2147215555 signed; 2147751741 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF for these values), and code field is 0x173D. Standard HRESULT severity rules classify the value as a failure. AllStat describes the value as “The document is offline.”
Contract boundary
This result belongs to opening an item represented by an offline, remote-storage or placeholder state. The decisive interpretation is that metadata exists locally but the bytes required for filtering are not hydrated or online. Keep the symbolic constant and method stage together in logs; its hexadecimal value alone cannot identify the owning transition or input.
The IFilter contract is stateful: GetChunk selects a chunk, then GetText or GetValue consumes content according to STAT_CHUNK flags. In the result investigation, method order and filter-instance ownership are therefore part of the evidence. This context narrows the responsible component without replacing the code-specific checks below.
Ways this state occurs
- Cloud placeholder hydration is unavailable; preserve the observation under the result correlation record.
- Remote storage media is not mounted; preserve the observation under the result correlation record.
- Offline files policy leaves content disconnected; preserve the observation under the result correlation record.
- Tiering moved data out of the online store; preserve the observation under the result correlation record.
The useful hypothesis for this HRESULT must explain both opening an item represented by an offline, remote-storage or placeholder state and the documented condition. Compare the failing case with a control that preserves offline/placeholder attributes and changes only hydration provider state; this prevents unrelated environment differences from dominating the result test.
Telemetry fields
- The result investigation should record offline/placeholder attributes.
- The result investigation should record hydration provider state.
- The result investigation should record volume and storage-tier identity.
- The result investigation should record policy governing recall by the filter host.
Capture offline/placeholder attributes before releasing objects, closing handles or reconnecting. Retain the raw HRESULT with hydration provider state, component version, UTC timestamp and correlation ID. Bound the result telemetry to diagnostic metadata because document content, credentials and unrestricted query text may be sensitive.
Verification sequence
- Confirm that the item identity exists and inspect its offline attributes. Associate this observation specifically with this result.
- Test an approved hydration operation under the service identity.
- Distinguish offline state from network-unreachable state.
- Record whether metadata-only indexing is still possible. Associate this observation specifically with it.
Change one variable per it control run. Preserve the component version and target identity, then alter only the condition described as metadata exists locally but the bytes required for filtering are not hydrated or online. This isolates whether it is causal rather than merely repeatable.
Safe continuation
Hydrate or bring the storage tier online, then create a new filtering attempt. Avoid uncontrolled recall of large datasets. Record whether opening an item represented by an offline, remote-storage or placeholder state produced any content, update or state transition before returning. If completion remains unknown, the path must not replay non-idempotent work until the owner confirms final state.
The retry gate for this HRESULT should be a concrete change in offline/placeholder attributes or hydration provider state. A timer alone cannot demonstrate that the result contract condition has changed.
Limits of the HRESULT
It does not mean the path is syntactically invalid, the file is locked, or access has been denied. Without the call boundary for opening an item represented by an offline, remote-storage or placeholder state, it also cannot identify which wrapper or configuration layer introduced the condition.
Distinguishing related codes
FILTER_E_UNREACHABLEThis resultthis result telemetry, preserve neighboring constants separately because the same visible symptom may require a different caller action, owner or recovery gate.
Developer and administrator actions
- At step 1 for this HRESULT, at the code boundary, keep offline/placeholder attributes beside the returned HRESULT
- At step 2 for this HRESULT, in telemetry, correlate hydration provider state with the target and component generation
- At step 3 for this HRESULT, for regression coverage, force the documented condition: metadata exists locally but the bytes required for filtering are not hydrated or online
- At step 4 for this HRESULT, for operations staff, expose the corrective state change rather than a generic retry button
- At step 5 for this HRESULT, after remediation, validate one known-good control and the original failing case
Practical case
A cloud placeholder is enumerated locally but content recall is disabled for the indexing service. Policy-aware telemetry explains the skipped body text. In this scenario, handling it at its real contract boundary prevents the application from collapsing a precise state into an unhelpful generic “search failed” message.
Official Microsoft references
- Microsoft: Content-Indexing values — official contract information relevant to it.
- Microsoft: filter handlers in Windows Search
- Microsoft: IFilter interface
- Microsoft: testing filter handlers
- Microsoft: Filter-Interface values
Looking for a different code? Search another status or error code.