| Previous | Next |
| ERROR_CLOUD_FILE_PROPERTY_VERSION_NOT_SUPPORTED | ERROR_CLOUD_FILE_NOT_IN_SYNC |
ERROR_NOT_A_CLOUD_FILE
Meaning and context of ERROR_NOT_A_CLOUD_FILE
Starting in Windows 10, version 1709, Windows provides the cloud files API. This API consists of several native Win32 and WinRT APIs that formalize support for cloud sync engines, and handles tasks such as creating and managing placeholder files and directories. Users of this API are typically sync providers and to some extent, Windows applications.
Reason: attribute letter "L" is missed after editing and probably there is only attribute letter "A".
"L": Indicates that the file has a reparse point. A reparse point is a special pointer for use by a file system filter. Azure File Sync uses reparse points to define to the Azure File Sync file system filter (StorageSync.sys) the cloud location where the file is stored. This supports seamless access. Users won't need to know that Azure File Sync is being used or how to get access to the file in your Azure file share. When a file is fully recalled, Azure File Sync removes the reparse point from the file.
You can see the attributes for all the files in a folder by adding the Attributes field to the table display of File Explorer. To do this, right-click on an existing column (for example, Size), select More, and then select Attributes from the drop-down list.
Where ERROR_NOT_A_CLOUD_FILE is returned
ERROR_NOT_A_CLOUD_FILE is Win32 system error 376 (0x00000178) from winerror.h. AllStat describes it as “The file is not a cloud file.”. For ERROR_NOT_A_CLOUD_FILE, the code is useful only together with the API that failed, because multiple Windows components can reuse system-error values while imposing different retry and cleanup rules.
Diagnostic sequence for ERROR_NOT_A_CLOUD_FILE
- Call GetLastError immediately after the failing API and save ERROR_NOT_A_CLOUD_FILE, the function name, all relevant flags, and the target path, handle, service, device, account, or policy object.
- Capture the component log that owns the a / cloud / file operation and retain the original numeric value before a framework converts it to an HRESULT or exception.
- For ERROR_NOT_A_CLOUD_FILE, compare preconditions with the API documentation and reproduce with a minimal request before changing system-wide configuration.
Retry ERROR_NOT_A_CLOUD_FILE only after the resource or state named in “The file is not a cloud file.” has changed. For ERROR_NOT_A_CLOUD_FILE, for invalid parameters, unsupported formats, missing objects, policy restrictions, and access failures, correct the input or configuration instead of immediately repeating the same call.
Official references for ERROR_NOT_A_CLOUD_FILE
Looking for a different code? Search another status or error code.