| 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 E_SKYDRIVE_ROOT_TARGET_OVERLAP is returned, ROOT_TARGET_CANNOT_INDEX concerns search/index capability; overlap concerns ownership of the directory tree.
For E_SKYDRIVE_ROOT_TARGET_OVERLAP, do not bypass the check with alternate path spelling or a junction.
Object and state boundary
When E_SKYDRIVE_ROOT_TARGET_OVERLAP 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 E_SKYDRIVE_ROOT_TARGET_OVERLAP 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 E_SKYDRIVE_ROOT_TARGET_OVERLAP investigation, nested or identical sync roots create ambiguous ownership of files, placeholders, notifications and upload state. For E_SKYDRIVE_ROOT_TARGET_OVERLAP, overlap can be textual or resolved through junctions and canonical volume paths.
For E_SKYDRIVE_ROOT_TARGET_OVERLAP, 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 E_SKYDRIVE_ROOT_TARGET_OVERLAP. | For E_SKYDRIVE_ROOT_TARGET_OVERLAP, 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 E_SKYDRIVE_ROOT_TARGET_OVERLAP. | For E_SKYDRIVE_ROOT_TARGET_OVERLAP, 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 E_SKYDRIVE_ROOT_TARGET_OVERLAP. | For E_SKYDRIVE_ROOT_TARGET_OVERLAP, 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 E_SKYDRIVE_ROOT_TARGET_OVERLAP. | For E_SKYDRIVE_ROOT_TARGET_OVERLAP, 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 for E_SKYDRIVE_ROOT_TARGET_OVERLAP | Hold constant |
|---|---|---|
| Same input, fresh object or connection | For E_SKYDRIVE_ROOT_TARGET_OVERLAP, if the result disappears, retained lifecycle or ownership state is implicated. | While diagnosing E_SKYDRIVE_ROOT_TARGET_OVERLAP, keep the original data, account, device, or timeline parameters unchanged. |
| Same object, reduced operation | For E_SKYDRIVE_ROOT_TARGET_OVERLAP, if the result follows one specific transition, statement, file, or ceremony step, the failure is localized. | While diagnosing E_SKYDRIVE_ROOT_TARGET_OVERLAP, remove only unrelated work and keep the first failing boundary visible. |
| Same stable item ID, second supported path | For E_SKYDRIVE_ROOT_TARGET_OVERLAP, a change separates local file-system/provider state from remote service state. | While diagnosing E_SKYDRIVE_ROOT_TARGET_OVERLAP, keep account, remote version and client build fixed. |
Step-by-step investigation
For E_SKYDRIVE_ROOT_TARGET_OVERLAP, 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 E_SKYDRIVE_ROOT_TARGET_OVERLAP 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 E_SKYDRIVE_ROOT_TARGET_OVERLAP.
- For
E_SKYDRIVE_ROOT_TARGET_OVERLAP: 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.