| Previous | Next |
| E_SYNCENGINE_STORAGE_SERVICE_PROVISIONING_FAILED | E_SYNCENGINE_STORAGE_SERVICE_BLOCKED |
E_SYNCENGINE_UNSUPPORTED_REPARSE_POINT
The scope of E_SYNCENGINE_UNSUPPORTED_REPARSE_POINT is Windows cloud-file and sync-engine infrastructure: the sync tree contains a reparse point whose semantics the engine does not support. Preserve 0x8802D009 beside the returning call before cleanup or retry creates a more generic secondary failure.
Wrong turns
Cloud Files itself uses controlled reparse points; this code concerns a tag or topology the engine does not support.
Do not delete every reparse point or assume it is a symbolic link.
Object and state
Reparse points are a mechanism, not a single object type. Junctions, symbolic links, mount points and provider placeholders have different tags and traversal rules; following them blindly can escape the sync root or create cycles.
Capture before retry
- Reparse tag and attributes.
- Source and resolved target.
- Position relative to sync root.
- Provider placeholder state.
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: Inspect the tag without traversing first.
- Next: Distinguish Cloud Files placeholders from links.
- Then: Reject escapes and cycles.
- Finally: Replace unsupported topology with ordinary supported directories.
Closure criteria
Closure requires supported placeholders synchronize, while unsupported links are detected before traversal and explained precisely; then repeat the next lifecycle operation to detect stale state.
Technical references
Looking for a different code? Search another status or error code.