| Previous | Next |
| ERROR_CLOUD_FILE_INCOMPATIBLE_HARDLINKS | ERROR_CLOUD_FILE_REQUEST_CANCELED |
ERROR_CLOUD_FILE_PROPERTY_LOCK_CONFLICT
Concurrent property access prevents a safe metadata update
ERROR_CLOUD_FILE_PROPERTY_LOCK_CONFLICT reports synchronization conflict in the cloud-file property store. It is not an ordinary file sharing violation and does not necessarily involve hydrated content. Two provider operations, repair paths, or property readers and writers can overlap in a way that prevents an atomic property update.
Log the placeholder FileIdentity, property identifier, operation type, and lifetime of every property transaction or provider lock. Look for callbacks that re-enter property management on the same placeholder or for cancellation paths that retain a lock. Serialize updates per placeholder and keep the critical section short; repeated parallel retries usually increase contention. If the conflict persists after all provider work ends, investigate stale or corrupt property metadata separately.
What to inspect
- Correlate property operations by FileIdentity and property identifier.
- Detect re-entrant callbacks and locks retained across remote I/O.
- Serialize conflicting updates and release lock state on cancel and failure paths.
References
- Microsoft: FileIdentity and PropertiesSize fields
- Microsoft: provider callback execution model
- Microsoft: synchronized placeholder updates
Looking for a different code? Search another status or error code.