| 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
When it is returned, 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 boundary
When it is returned, 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. During a this result investigation, 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.
During a this result investigation, 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.
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.
Capture before retry
| Capture | Diagnostic value |
|---|---|
| Candidate and existing canonical paths for it. | This identifies the exact object or resource generation involved and helps test the Windows cloud-file and sync-engine infrastructure boundary. |
| Volume/file IDs for it. | This places the failure on the lifecycle or transaction timeline and helps test the Windows cloud-file and sync-engine infrastructure boundary. |
| Junctions or reparse points for it. | This separates caller input from environment and service state and helps test the Windows cloud-file and sync-engine infrastructure boundary. |
| Registered provider ownership for it. | This provides a stable comparison across retries or another machine and helps test the Windows cloud-file and sync-engine infrastructure boundary. |
Controlled comparisons
| Control | Interpretation | Hold constant |
|---|---|---|
| Same input, fresh object or connection | If the result disappears, retained lifecycle or ownership state is implicated. | While diagnosing this result, keep the original data, account, device, or timeline parameters unchanged. |
| Same object, reduced operation | If the result follows one specific transition, statement, file, or ceremony step, the failure is localized. | While diagnosing this result, remove only unrelated work and keep the first failing boundary visible. |
| Same stable item ID, second supported path | A change separates local file-system/provider state from remote service state. | While diagnosing it, 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 for it 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
The references below define the API family or storage/protocol behavior used to interpret it.
- Microsoft: Build a Cloud Files sync engine
- Microsoft: StorageProviderSyncRootManager
- Microsoft: Reparse points
- Microsoft: Cloud Filter API reference
Looking for a different code? Search another status or error code.