What does HRESULT 0x80041828 (CI_E_CONFIG_DISK_FULL) mean?

 
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. For CI_E_CONFIG_DISK_FULL, 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

CI_E_CONFIG_DISK_FULL 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. For CI_E_CONFIG_DISK_FULL, keep the symbolic constant and method stage together in logs; its hexadecimal value alone cannot identify the owning transition or input.

For CI_E_CONFIG_DISK_FULL, the legacy content-index helper layer has explicit object, catalog and service states. In the CI_E_CONFIG_DISK_FULL 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 CI_E_CONFIG_DISK_FULL, the configured maximum is reached
  • At step 2 for CI_E_CONFIG_DISK_FULL, retention or crawl scope grows beyond planning
  • At step 3 for CI_E_CONFIG_DISK_FULL, obsolete data has not been compacted
  • At step 4 for CI_E_CONFIG_DISK_FULL, the limit was lowered below current usage

The useful hypothesis for CI_E_CONFIG_DISK_FULL 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 CI_E_CONFIG_DISK_FULL test.

Data for diagnosis

  • CI_E_CONFIG_DISK_FULL: Configured limit and current catalog size.
  • CI_E_CONFIG_DISK_FULL: Filesystem free space.
  • CI_E_CONFIG_DISK_FULL: Growth trend and largest scopes.
  • CI_E_CONFIG_DISK_FULL: Recent policy changes.

For CI_E_CONFIG_DISK_FULL, 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 CI_E_CONFIG_DISK_FULL telemetry to diagnostic metadata because document content, credentials and unrestricted query text may be sensitive.

Investigation order

  1. Compare policy ceiling with physical capacity. Associate this observation specifically with CI_E_CONFIG_DISK_FULL.
  2. Identify which scopes drive growth. Associate this observation specifically with CI_E_CONFIG_DISK_FULL.
  3. Check supported maintenance/compaction options. Associate this observation specifically with CI_E_CONFIG_DISK_FULL.
  4. Do not confuse the limit with filesystem full. Associate this observation specifically with CI_E_CONFIG_DISK_FULL.

Change one variable per CI_E_CONFIG_DISK_FULL 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 CI_E_CONFIG_DISK_FULL is causal rather than merely repeatable.

Correct response

Reduce indexed scope, perform supported maintenance, or raise the limit after capacity review; then resume updates. For CI_E_CONFIG_DISK_FULL, 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 CI_E_CONFIG_DISK_FULL path must not replay non-idempotent work until the owner confirms final state.

The retry gate for CI_E_CONFIG_DISK_FULL should be a concrete change in configured limit and current catalog size or filesystem free space. A timer alone cannot demonstrate that the CI_E_CONFIG_DISK_FULL 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, CI_E_CONFIG_DISK_FULL also cannot identify which wrapper or configuration layer introduced the condition.

Related HRESULT values

CI_E_DISK_FULL is physical capacity failure; CI_E_CONFIG_DISK_FULL is an intentional configured ceiling. In CI_E_CONFIG_DISK_FULL telemetry, preserve neighboring constants separately because the same visible symptom may require a different caller action, owner or recovery gate.

Developer and administrator actions

  • For CI_E_CONFIG_DISK_FULL, check At the code boundary, keep configured limit and current catalog size beside the returned HRESULT.
  • For CI_E_CONFIG_DISK_FULL, check In telemetry, correlate filesystem free space with the target and component generation.
  • For CI_E_CONFIG_DISK_FULL, check For regression coverage, force the documented condition: policy prevents catalog growth even though the filesystem may still have free space.
  • For CI_E_CONFIG_DISK_FULL, check For operations staff, expose the corrective state change rather than a generic retry button.
  • For CI_E_CONFIG_DISK_FULL, 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 CI_E_CONFIG_DISK_FULL at its real contract boundary prevents the application from collapsing a precise state into an unhelpful generic “search failed” message.

Official Microsoft references

Looking for a different code? Search another status or error code.