| Previous | Next |
| E_SKYDRIVE_ROOT_TARGET_OVERLAP | E_SKYDRIVE_FILE_NOT_UPLOADED |
E_SKYDRIVE_ROOT_TARGET_CANNOT_INDEX
Within Windows cloud-file and sync-engine infrastructure, E_SKYDRIVE_ROOT_TARGET_CANNOT_INDEX reports that the proposed sync-root location cannot participate in required indexing. Diagnosis of this result should follow the original owner and generation rather than treating the visible symptom as the cause.
Mechanism behind the code
During a this result investigation, a Windows sync engine coordinates local NTFS objects, provider metadata, remote identifiers, quota and naming rules, placeholder hydration, network authentication, and asynchronous upload or download state. The same Explorer action can cross several of those boundaries, so diagnosis must retain the first failing stage rather than treating every code as a generic connectivity problem.
Shell and sync integration may depend on the target being indexable., exclusion policy, volume capability, permissions, or location type can make a folder usable for ordinary files but unsuitable as the managed root.
The first owner to inspect is the local sync root, placeholder state, file-system operation, provider request, network exchange, account policy, or remote storage operation that produced the HRESULT.
High-value telemetry
| Capture | Diagnostic value |
|---|---|
| Target canonical path for it. | This places the failure on the lifecycle or transaction timeline and helps test the Windows cloud-file and sync-engine infrastructure boundary. |
| Windows Search/indexing policy for it. | This separates caller input from environment and service state and helps test the Windows cloud-file and sync-engine infrastructure boundary. |
| Volume capability for it. | This provides a stable comparison across retries or another machine and helps test the Windows cloud-file and sync-engine infrastructure boundary. |
| Effective service and user access for it. | This identifies the exact object or resource generation involved and helps test the Windows cloud-file and sync-engine infrastructure boundary. |
Decision table
- Second supported path for the same stable item: for it, a changed result separates retained object, connection, path, host, or device state from the original input. Hold constant: for it, keep account, remote item version, and client build fixed.
- Reduced failing operation: If this result follows the reduced step, the rejecting transition is localized. Hold constant: for it, retain target canonical path and remove only unrelated work.
- Targeted corrective control: Use this as a diagnostic branch rather than a blanket workaround: check whether the location can be indexed. Hold constant: for it, keep the original this result sample available for the final regression test.
Safe reduction procedure
When it is returned, use a disposable control object, repository copy, file, or device association where the subsystem permits it.
- First: Check whether the location can be indexed.
- Next: Compare a normal local NTFS folder.
- Then: Remove policy exclusions only through approved administration.
- Finally: Re-register after confirming index visibility.
Do not erase the distinction
During a it investigation, FILE_SYSTEM_NOT_SUPPORTED is a storage-format failure; CANNOT_INDEX is a search/integration capability failure.
Do not rebuild the entire search index before proving the target is eligible.
Successful outcome
Verify it with the original scenario, one boundary case, and one deliberate failure; success means the chosen folder is indexable and remains registered after service and system restart.
Technical references
The references below define the API family or storage/protocol behavior used to interpret it.
- Microsoft: Build a Cloud Files sync engine
- Microsoft: Determine cloud placeholder state
- Microsoft: Restrictions and limitations in OneDrive and SharePoint
- Microsoft: StorageProviderSyncRootManager
Looking for a different code? Search another status or error code.