Skip to content

Commit 671d36f

Browse files
Update file-sync-troubleshoot-sync-errors.md
Added ECS_E_SYNC_ITEM_SKIP_CONSTRAINT_CONFLICT_NOT_ALLOWED
1 parent 435ecb5 commit 671d36f

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

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
@@ -211,6 +211,7 @@ If a file or directory fails to sync due to an error, an event is logged in the
211211
| 0x80c8604b | -2134351797 | ECS_E_AZURE_FILE_SHARE_FILE_NOT_FOUND | The specified Azure file wasn't found in the file share. This issue might occur if the file has been deleted and sync isn't aware of the change. | No action required. Sync will stop logging this error once change detection detects the file was deleted. |
212212
| 0x80c80201 | -2134375935 | ECS_E_SYNC_UNPROCESSABLE_ITEM_REPARSEPOINT | The sync failed due to the presence of a reparse point. | Remove the reparse point or replace it with regular file content before attempting the sync again. |
213213
| 0x80c80362 | -2134375582 | ECS_E_ITEM_PATH_COMPONENT_HAS_TRAILING_DOT | The item failed to sync because one of its path component has trailing dot(s). | Rename the item removing any trailing dot(s) that exist in the path. |
214+
| 0x80c8024e | -2134375858 | ECS_E_SYNC_ITEM_SKIP_CONSTRAINT_CONFLICT_NOT_ALLOWED | This error indicates a constraint conflict that was detected but was unable to be reported. The item will be skipped. | If the error persists, create a support request. |
214215

215216
### Handling unsupported characters
216217

0 commit comments

Comments
 (0)