Merge pull request #8087 from simonxjx/simon-3

AB#3596: Post Edit PR#8078

Author: Simonx Xu

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

@@ -4,10 +4,10 @@ description: Troubleshoot common issues with monitoring sync health and resolvin
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: troubleshooting
-ms.date: 01/03/2025
+ms.date: 01/23/2025
 ms.author: kendownie
 ms.custom: sap:File Sync, devx-track-azurepowershell
-ms.reviewer: v-weizhu
+ms.reviewer: v-weizhu, vritikanaik
 ---
 # Troubleshoot Azure File Sync sync health and errors
 
@@ -210,7 +210,7 @@ If a file or directory fails to sync due to an error, an event is logged in the
 | 0X80C80342 | -2134375614 | ECS_E_SYNC_CUSTOM_METADATA_VERSION_NOT_SUPPORTED | The sync database has custom metadata with a version higher than the supported version. | Please upgrade the File Sync agent to the latest version. If the error persists after upgrading the agent, create a support request. |
 | 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. |
 | 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. |
-| 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. |
+| 0x80c80362 | -2134375582 | ECS_E_ITEM_PATH_COMPONENT_HAS_TRAILING_DOT | The item failed to sync because one of its path components has trailing dots. | Rename the item by removing any trailing dots that appear in the path. |
 | 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. |
 
 ### Handling unsupported characters

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-sync-group-management.md

@@ -4,9 +4,9 @@ description: Troubleshoot common issues in managing Azure File Sync sync groups,
 author: khdownie
 ms.service: azure-file-storage
 ms.topic: troubleshooting
-ms.date: 01/13/2025
+ms.date: 01/23/2025
 ms.author: kendownie
-ms.reviewer: v-weizhu
+ms.reviewer: v-weizhu, vritikanaik
 ms.custom: sap:File Sync
 ---
 # Troubleshoot Azure File Sync sync group management
@@ -83,7 +83,7 @@ This error occurs if the server endpoint path is on the system volume and cloud
 
 This error occurs if the server endpoint path specified isn't valid. Verify the server endpoint path specified is a locally attached NTFS volume. Note, Azure File Sync doesn't support mapped drives as a server endpoint path.
 
-<a id="-2147024894"></a>**Server endpoint creation fails, with this error: "MgmtServerJobFailed" (Error code: -2147024875 or 0x80070015)**
+<a id="-2147024875"></a>**Server endpoint creation fails, with this error: "MgmtServerJobFailed" (Error code: -2147024875 or 0x80070015)**
 
 This error occurs if the server endpoint path specified isn't valid. Verify the server endpoint path specified is a locally attached NTFS volume. Note, Azure File Sync doesn't support mapped drives as a server endpoint path.
 
@@ -123,7 +123,7 @@ This error occurs if the server is offline or doesn't have network connectivity.
 
 <a id="-2134347720"></a>**Server endpoint deletion fails, with this error: "MgmtFileShareSnapshotCountExceeded" (Error code: -2134347720 or 0x80c87038)**
 
-The error occurs when the ShareSnapshotCount exceeds the limit. Azure Files Sync takes a snapshot of the Azure file share as a backup before creating the server endpoint. This snapshot can be used to restore the share to the state before the server endpoint was created. The snapshot is not removed automatically after the server endpoint is created, so you can delete it manually if you don't need it. You can find the snapshots created by Azure File Sync by looking at the snapshots for the Azure file share and checking for AzureFileSync in the Initiator column.
+The error occurs when the File Share Snapshot Count exceeds the limit. Azure File Sync takes a snapshot of the Azure file share as a backup before creating the server endpoint. This snapshot can be used to restore the share to the state before the server endpoint is created. The snapshot isn't removed automatically after the server endpoint is created. You can delete it manually if it's no longer needed. To identify snapshots created by Azure File Sync, examine the snapshots of the Azure file share and look for "AzureFileSync" in the Initiator column.
 
 ## Server endpoint health