| Previous | Next |
| E_SKYDRIVE_ROOT_TARGET_FILE_SYSTEM_NOT_SUPPORTED | E_SKYDRIVE_ROOT_TARGET_CANNOT_INDEX |
E_SKYDRIVE_ROOT_TARGET_OVERLAP
The scope of E_SKYDRIVE_ROOT_TARGET_OVERLAP is Windows cloud-file and sync-engine infrastructure: the requested sync-root location overlaps another managed location. Preserve 0x80270261 beside the returning call before cleanup or retry creates a more generic secondary failure.
Wrong turns
ROOT_TARGET_CANNOT_INDEX concerns search/index capability; overlap concerns ownership of the directory tree.
Do not bypass the check with alternate path spelling or a junction.
Object and state
Nested or identical sync roots create ambiguous ownership of files, placeholders, notifications and upload state. Overlap can be textual or resolved through junctions and canonical volume paths.
Inspect the local sync root, placeholder state, file-system operation, provider request, network exchange, account policy, or remote storage operation that produced the HRESULT.
Capture before retry
- Candidate and existing canonical paths.
- Volume/file IDs.
- Junctions or reparse points.
- Registered provider ownership.
Controlled comparisons
| Control | Interpretation | Hold constant |
|---|---|---|
| Same stable item ID, second supported path | A change separates local file-system/provider state from remote service state. | Keep account, remote version and client build fixed. |
Step-by-step investigation
The investigation should change one variable at a time and keep the original failing sample.
- First: Resolve final paths and file IDs.
- Next: Enumerate existing sync-root registrations.
- Then: Choose a disjoint directory.
- Finally: Test rename and move events at the boundary.
Closure criteria
Closure requires each managed tree has one provider owner and boundary moves are handled deterministically; then repeat the next lifecycle operation to detect stale state.
Technical references
Looking for a different code? Search another status or error code.