Skip to content

Commit 42afd1e

Browse files
authored
Merge pull request #8896 from MicrosoftDocs/main
Auto push to live 2025-05-08 18:07:11
2 parents 7462f67 + ee52ba6 commit 42afd1e

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-errors.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -190,6 +190,7 @@ If a file or directory fails to sync due to an error, an event is logged in the
190190
| 0x80070005 | -2147024891 | ERROR_ACCESS_DENIED | The file has a delete pending state. | No action required. File will be deleted once all open file handles are closed. |
191191
| 0x80c86044 | -2134351804 | ECS_E_AZURE_AUTHORIZATION_FAILED | The file can't be synced because the firewall and virtual network settings on the storage account are enabled, and the server doesn't have access to the storage account. | Add the Server IP address or virtual network by following the steps documented in the [Configure firewall and virtual network settings](/azure/storage/file-sync/file-sync-deployment-guide?tabs=azure-portal#optional-configure-firewall-and-virtual-network-settings) section in the deployment guide. |
192192
| 0x8000ffff | -2147418113 | E_UNEXPECTED | The file can't be synced due to an unexpected error. | If the error persists for several days, please open a support case. |
193+
| 0x80c8308f | -2134364017 | ECS_E_ETAG_VERIFCATION_FAILED | The file can't be synced because ETag verification with the target has failed. | If the error persists for several days, please open a support case. |
193194
| 0x80070020 | -2147024864 | ERROR_SHARING_VIOLATION | The file can't be synced because it's in use. The file will be synced when it's no longer in use. | No action required. |
194195
| 0x80c80017 | -2134376425 | ECS_E_SYNC_OPLOCK_BROKEN | The file was changed during sync, so it needs to be synced again. | No action required. |
195196
| 0x80070017 | -2147024873 | ERROR_CRC | The file can't be synced due to CRC error. This error can occur if a tiered file was not recalled prior to deleting a server endpoint or if the file is corrupt. | To resolve this issue, see [Tiered files are not accessible on the server](file-sync-troubleshoot-cloud-tiering.md#tiered-files-are-not-accessible-on-the-server) to remove tiered files that are orphaned. If the error continues to occur after removing orphaned tiered files, run [chkdsk](/windows-server/administration/windows-commands/chkdsk) on the volume. |

0 commit comments

Comments
 (0)