| Previous | Next |
| FSRM_E_INVALID_FOLDER_PROPERTY_STORE | FSRM_E_PROPERTY_MUST_APPLY_TO_FILES |
FSRM_E_REBUILDING_FODLER_TYPE_INDEX
The Folder Usage index is being rebuilt
This HRESULT reports a transient service state: File Server Resource Manager is rebuilding the index of Folder Usage property values. The constant contains the historical spelling FODLER; callers must use the symbol exactly as published. The result is not evidence that a requested folder or property value is invalid.
The documented condition is: “File Server Resource Manager is rebuilding the index of Folder Usage property values.” The wording should be interpreted at this FSRM stage, not as a generic file-system or COM failure.
Where the failure point lies
Folder Usage values can be used as namespace selectors for file-management jobs and other classification workflows. While the supporting index is being reconstructed, FSRM cannot reliably answer operations that depend on that index. The correct boundary is index availability, not the validity of one job definition or one folder path.
Likely causes to separate
- FSRM started an index rebuild after configuration migration, service maintenance, or a detected inconsistency.
- A large set of Folder Usage property changes requires the service to regenerate indexed mappings.
- The service restarted while a prior index update was incomplete and resumed reconstruction.
- Storage latency or resource pressure extends a normally brief rebuild window.
Evidence worth preserving
- Capture the FSRM event that announces the rebuild, its start time, and any progress or completion event.
- Record which operation required the Folder Usage index, such as enumerating a namespace or validating a file-management job scope.
- Measure whether the same request succeeds after the rebuild without any configuration change.
- Check service CPU, memory, database volume latency, and free space if the rebuilding state persists unusually long.
Diagnostic sequence
- Confirm that the service remains running and that the event log shows active rebuild work rather than repeated restarts.
- Avoid modifying Folder Usage definitions during the test because configuration churn can obscure whether the original rebuild completes.
- Use a direct local path control operation that does not depend on Folder Usage to verify that unrelated FSRM functions remain available.
- Escalate only when the index never reaches a completed state or the service logs a separate database, disk, or internal error.
Retry and recovery
Use a bounded delayed retry after the index completion signal. Do not treat immediate retry loops as recovery; they add load while the same prerequisite is unavailable. If the service remains in rebuilding state, preserve logs and investigate the FSRM database volume and service health before restarting or recreating configuration.
What this HRESULT does not establish
The code does not mean the index has lost Folder Usage values, nor does it prove the FSRM configuration is corrupt. It only states that the indexed view is not currently ready. Completion must be verified before making conclusions about missing folders.
Difference from nearby FSRM results
FSRM_E_INVALID_FOLDER_PROPERTY_STORE concerns invalid persisted metadata for a folder. This result instead describes a service-wide maintenance state for the Folder Usage index.
Practical scenario
After importing FSRM configuration on a server with many classified folders, an automation script immediately enumerates jobs by Folder Usage and receives this HRESULT. The script waits for the rebuild completion event, re-queries once, and obtains the expected objects without changing the imported definitions.
Guidance for software and telemetry
Clients should classify this value as retryable with backoff and a deadline. Telemetry should include rebuild duration and service generation so operators can distinguish a normal maintenance interval from a rebuild loop.
Official Microsoft references
Looking for a different code? Search another status or error code.