| Previous | Next |
| ERROR_CLOUD_FILE_UNSUCCESSFUL | ERROR_CLOUD_FILE_IN_USE |
ERROR_CLOUD_FILE_NOT_UNDER_SYNC_ROOT
The path is not contained by the sync root required for this operation
ERROR_CLOUD_FILE_NOT_UNDER_SYNC_ROOT means the requested CFAPI operation targets an object that is not below a registered sync-root directory. Placeholder creation and management are scoped to a sync root because registration supplies the provider identity and policies governing that namespace.
Resolve the final filesystem path after junctions, mount points, and renames, then compare it with the registered root used by the provider. Do not rely only on a textual path prefix: the object may have moved, the account root may have been reconfigured, or a helper may be using a stale path. Registering arbitrary parent directories merely to bypass the error expands provider scope and can associate unrelated files with the wrong cloud identity.
What to inspect
- Resolve the actual target path and volume before invoking CFAPI.
- Compare it with the root path and provider identity currently registered.
- Refresh cached paths after account moves, renames, or sync-root reconfiguration.
References
- Microsoft: sync-root path registration
- Microsoft: creating placeholders under a sync root
- Microsoft: connecting by SyncRootPath
Looking for a different code? Search another status or error code.