| Previous | Next |
| ERROR_CLOUD_FILE_PROVIDER_NOT_RUNNING | ERROR_CLOUD_FILE_METADATA_TOO_LARGE |
ERROR_CLOUD_FILE_METADATA_CORRUPT
The problem is in one placeholder's platform metadata
ERROR_CLOUD_FILE_METADATA_CORRUPT applies to metadata attached to a cloud placeholder, such as its Cloud Files identity and platform-maintained state. It differs from sync-root metadata corruption, which affects registration of the entire root. Placeholder information can normally be queried with CfGetPlaceholderInfo; the returned standard information includes file identity, pin state, in-sync state, local data ranges, and property-store size.
Identify whether the failure follows one file or all entries below the root. For an isolated object, compare its remote identity with the provider database and consider recreating the placeholder from authoritative cloud metadata through supported create, update, convert, or revert operations. Do not infer that user file bytes are corrupt merely from this status: the damaged structure can be metadata even when hydrated content remains readable.
What to inspect
- Query placeholder information and record which information class fails.
- Compare the affected file identity with the provider's remote-object mapping.
- Recreate only the affected placeholder after preserving unsynchronized local data.
References
- Microsoft: querying placeholder information
- Microsoft: standard placeholder metadata fields
- Microsoft: updating an existing placeholder
Looking for a different code? Search another status or error code.