| Previous | Next |
| ERROR_DAX_MAPPING_EXISTS | ERROR_CLOUD_FILE_METADATA_CORRUPT |
ERROR_CLOUD_FILE_PROVIDER_NOT_RUNNING
The placeholder request has no running provider to answer it
ERROR_CLOUD_FILE_PROVIDER_NOT_RUNNING is returned when an operation needs the sync provider but the provider process is not active or has not established its CFAPI connection. Registration alone is insufficient: CfConnectSyncRoot creates the bidirectional channel and callback table used for fetch, validation, rename, delete, and other placeholder requests.
Check provider service or startup logs before treating the cloud file as corrupt. A provider can be installed and the sync root can remain registered while no process is connected. Verify that initialization reached CfConnectSyncRoot, that the call returned a connection key, and that the process did not exit after registration or authentication setup. Retrying the file operation is useful only after the provider is ready to accept callbacks.
What to inspect
- Verify that the provider process or service is running under the expected user session.
- Log the result of CfConnectSyncRoot and retain the connection key per sync root.
- Distinguish provider startup failure from a remote network or account-authentication failure.
References
- Microsoft: CfConnectSyncRoot communication channel
- Microsoft: callback types serviced by a provider
- Microsoft sample: CloudMirror provider lifecycle
Looking for a different code? Search another status or error code.