| Previous | Next |
| CI_E_CARDINALITY_MISMATCH | CI_E_DISTRIBUTED_GROUPBY_UNSUPPORTED |
CI_E_CONFIG_DISK_FULL
The catalog reached its configured storage limit
CI_E_CONFIG_DISK_FULL is HRESULT 0x80041828 (-2147215320 signed; 2147751976 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF for these values), and code field is 0x1828. Standard HRESULT severity rules classify the value as a failure. AllStat describes the value as “The disk has reached its configured space limit.”
State represented by the HRESULT
This result belongs to admitting new index data while enforcing an administrative size ceiling. The decisive interpretation is that policy prevents catalog growth even though the filesystem may still have free space. Keep the symbolic constant and method stage together in logs; its hexadecimal value alone cannot identify the owning transition or input.
The legacy content-index helper layer has explicit object, catalog and service states. In the result investigation, a generic retry can hide lifecycle, ordering or policy defects. This context narrows the responsible component without replacing the code-specific checks below.
Likely triggers
- At step 1 for it, the configured maximum is reached
- At step 2 for it, retention or crawl scope grows beyond planning
- At step 3 for it, obsolete data has not been compacted
- At step 4 for it, the limit was lowered below current usage
The useful hypothesis for it must explain both admitting new index data while enforcing an administrative size ceiling and the documented condition. Compare the failing case with a control that preserves configured limit and current catalog size and changes only filesystem free space; this prevents unrelated environment differences from dominating the result test.
Data for diagnosis
- This result: Configured limit and current catalog size.
- This result: Filesystem free space.
- This result: Growth trend and largest scopes.
- It: Recent policy changes.
Capture configured limit and current catalog size before releasing objects, closing handles or reconnecting. Retain the raw HRESULT with filesystem free space, 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.
Investigation order
- Compare policy ceiling with physical capacity. Associate this observation specifically with it.
- Identify which scopes drive growth. Associate this observation specifically with it.
- Check supported maintenance/compaction options. Associate this observation specifically with it.
- Do not confuse the limit with filesystem full. 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 policy prevents catalog growth even though the filesystem may still have free space. This isolates whether it is causal rather than merely repeatable.
Correct response
Reduce indexed scope, perform supported maintenance, or raise the limit after capacity review; then resume updates. Record whether admitting new index data while enforcing an administrative size ceiling 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 it should be a concrete change in configured limit and current catalog size or filesystem free space. A timer alone cannot demonstrate that the result contract condition has changed.
Scope of the signal
It does not mean the storage volume has no free blocks. Without the call boundary for admitting new index data while enforcing an administrative size ceiling, it also cannot identify which wrapper or configuration layer introduced the condition.
Related HRESULT values
CI_E_DISK_FULL is physical capacity failure; it is an intentional configured ceiling. In it telemetry, preserve neighboring constants separately because the same visible symptom may require a different caller action, owner or recovery gate.
Developer and administrator actions
- check At the code boundary, keep configured limit and current catalog size beside the returned HRESULT.
- check In telemetry, correlate filesystem free space with the target and component generation.
- check For regression coverage, force the documented condition: policy prevents catalog growth even though the filesystem may still have free space.
- check For operations staff, expose the corrective state change rather than a generic retry button.
- check After remediation, validate one known-good control and the original failing case.
Example in a pipeline
A catalog limit remains at 10 GB after the indexed share triples. Capacity planning adjusts scope and ceiling before resuming ingestion. 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 helper-function values — official contract information relevant to it.
- Microsoft: Content-Indexing values
- Microsoft: HRESULT values
- Microsoft: Windows Search SQL syntax
Looking for a different code? Search another status or error code.