| 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
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.
High-value telemetry
- Target canonical path.
- Windows Search/indexing policy.
- Volume capability.
- Effective service and user access.
Decision table
- Second supported path for the same stable item: a changed result separates retained object, connection, path, host, or device state from the original input. Hold constant: 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: 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: keep the original failing sample available for the final regression test.
Safe reduction procedure
Use a disposable control object, repository copy, file, or device association where the subsystem permits that safely.
- 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 an 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
Looking for a different code? Search another status or error code.