| Previous | Next |
| STATUS_CLOUD_FILE_NOT_IN_SYNC | STATUS_CLOUD_FILE_NOT_SUPPORTED |
STATUS_CLOUD_FILE_ALREADY_CONNECTED
This is a local connection-lifecycle conflict. A sync root may be registered persistently, but only one active CfConnectSyncRoot connection may exist for the same root path. The status does not say that the remote account is already signed in or that the local directory is corrupt.
Look for a second provider instance, an incomplete shutdown, or a supervisor that restarted the process before the previous instance released its connection. Registering the root again is not the normal fix; establish which process owns the connection and restore a single owner for its callbacks and connection key.
Useful checks
- Log the sync-root path and provider process identity on connect and disconnect.
- Keep a distinct connection key for every root; do not use one root's key for another.
- Allow normal shutdown to call
CfDisconnectSyncRoot; unexpected termination is cleaned up by the platform.
Relevant documentation
- CfConnectSyncRoot states that only one connection may exist for a sync-root path.
- CfDisconnectSyncRoot describes normal disconnect and cleanup after an unexpected provider exit.
Looking for a different code? Search another status or error code.