| Previous | Next |
| ERROR_GDI_HANDLE_LEAK | ERROR_CLOUD_FILE_PROPERTY_VERSION_NOT_SUPPORTED |
ERROR_CLOUD_FILE_TOO_MANY_PROPERTY_BLOBS
The property store contains too many separate entries
ERROR_CLOUD_FILE_TOO_MANY_PROPERTY_BLOBS is a count limit, not a byte-size limit. A design can therefore hit it even when every individual property is small. The standard placeholder information exposes only the aggregate property-store size; provider diagnostics must retain the identifiers and lifecycle of properties it adds or replaces.
Look for code that allocates a new property identifier on every synchronization pass instead of updating a stable entry, or that leaves obsolete schema versions behind after migration. Consolidate related fields where the property contract allows it and remove superseded provider data through supported operations. Increasing file size, hydrating content, or freeing ordinary disk space does not reduce the number of property blobs.
What to inspect
- Track property identifiers over repeated update cycles for the same placeholder.
- Confirm that migrations replace old versions instead of appending indefinitely.
- Separate the property-count problem from PropertiesSize and disk-capacity checks.
References
- Microsoft: PropertiesSize and placeholder standard information
- Microsoft: querying placeholder characteristics
- Microsoft: updating placeholder characteristics
Looking for a different code? Search another status or error code.