| Previous | Next |
| STATUS_CLOUD_FILE_ACCESS_DENIED | STATUS_CLOUD_FILE_PROPERTY_LOCK_CONFLICT |
STATUS_CLOUD_FILE_INCOMPATIBLE_HARDLINKS
Cloud Files does not treat hard links as an ordinary filename alias. By default, placeholders do not allow hard links. A provider that can preserve their semantics must opt in through the root's hard-link policy, and even then links are limited to compatible scope rules.
Do not work around this status by copying placeholder metadata to a second link. Determine whether the provider supports hard links, whether both paths are in the same sync root, and whether the operation would require hydration or reversion to a normal file. The policy is designed to prevent one remote identity from acquiring an unsupported local topology.
Useful checks
- Inspect the root's
CF_HARDLINK_POLICYrather than assuming NTFS hard-link support is sufficient. - Check whether the linked paths are inside the same sync root or outside all roots.
- For an unsupported topology, use a copy or provider-supported duplicate instead of forcing a hard link.
Relevant documentation
- CF_HARDLINK_POLICY defines compatible hard-link behavior and this failure.
- CF_SYNC_POLICIES explains hydration and reversion effects when hard links cross sync-root scope.
Looking for a different code? Search another status or error code.