You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/file-sync/file-sync-troubleshoot-sync-errors.md
+76-15Lines changed: 76 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -175,6 +175,17 @@ The table below contains all of the unicode characters Azure File Sync does not
175
175
176
176
Sync sessions might fail for various reasons including the server being restarted or updated, VSS snapshots, etc. Although this error looks like it requires follow-up, it's safe to ignore this error unless it persists over a period of several hours.
177
177
178
+
<aid="-2134375780"></a>**The file sync session was cancelled by the volume snapshot sync session that runs once a day to sync files with open handles.**
179
+
180
+
| Error | Code |
181
+
|-|-|
182
+
|**HRESULT**| 0x80c8029c |
183
+
|**HRESULT (decimal)**| -2134375780 |
184
+
|**Error string**| ECS_E_SYNC_CANCELLED_BY_VSS |
185
+
|**Remediation required**| No |
186
+
187
+
No action required. This error should automatically resolve. If the error persists for more than a day, create a support request.
188
+
178
189
<aid="-2147012889"></a>**A connection with the service could not be established.**
179
190
180
191
| Error | Code |
@@ -205,6 +216,13 @@ Sync sessions might fail for various reasons including the server being restarte
@@ -533,20 +551,6 @@ This error can happen if your organization is using a TLS terminating proxy or i
533
551
534
552
By setting this registry value, the Azure File Sync agent will accept any locally trusted TLS/SSL certificate when transferring data between the server and the cloud service.
535
553
536
-
<a id="-2147012894"></a>**A connection with the service could not be established.**
> Once network connectivity to the Azure File Sync service is restored, sync might not resume immediately. By default, Azure File Sync will initiate a sync session every 30 minutes if no changes are detected within the server endpoint location. To force a sync session, restart the Storage Sync Agent (FileSyncSvc) service, or make a change to a file or directory within the server endpoint location.
549
-
550
554
<a id="-2147012721"></a>**Sync failed because the server was unable to decode the response from the Azure File Sync service**
551
555
552
556
| Error | Code |
@@ -632,7 +636,9 @@ This error occurs because the server endpoint deletion failed and the endpoint i
Sync sessions fail with one of these errors because either the volume has insufficient disk space or disk quota limit is reached. This error commonly occurs because files outside the server endpoint are using up space on the volume. Free up space on the volume by adding additional server endpoints, moving files to a different volume, or increasing the size of the volume the server endpoint is on. If a disk quota is configured on the volume using [File Server Resource Manager](/windows-server/storage/fsrm/fsrm-overview) or [NTFS quota](/windows-server/administration/windows-commands/fsutil-quota), increase the quota limit.
639
+
Sync sessions fail with one of these errors because either the volume has insufficient disk space or disk quota limit is reached. This error commonly occurs because files outside the server endpoint are using up space on the volume. Check the available disk space on the server. You can free up space on the volume by adding additional server endpoints, moving files to a different volume, or increasing the size of the volume the server endpoint is on. If a disk quota is configured on the volume using [File Server Resource Manager](/windows-server/storage/fsrm/fsrm-overview) or [NTFS quota](/windows-server/administration/windows-commands/fsutil-quota), increase the quota limit.
640
+
641
+
If cloud tiering is enabled for the server endpoint, verify the files are syncing to the Azure file share to avoid running out of disk space.
636
642
637
643
<aid="-2134364145"></a><aid="replica-not-ready"></a>**The service isn't yet ready to sync with this server endpoint.**
638
644
@@ -1226,6 +1232,61 @@ Check if the Azure file share exists in the storage account.
1226
1232
1227
1233
No action required. This error should automatically resolve. If the error persists for several days, create a support request.
1228
1234
1235
+
<aid="-2134347516"></a>**The volume is offline. Either it is removed, not ready or not connected.**
1236
+
1237
+
| Error | Code |
1238
+
|-|-|
1239
+
|**HRESULT**| 0x80c87104 |
1240
+
|**HRESULT (decimal)**| -2134347516 |
1241
+
|**Error string**| ECS_E_VOLUME_OFFLINE |
1242
+
|**Remediation required**| Yes |
1243
+
1244
+
Please verify the volume where the server endpoint is located is attached to the server.
Check the private endpoint configuration and allow access to the file sync service. [Learn more](file-sync-firewall-and-proxy.md#test-network-connectivity-to-service-endpoints).
1256
+
1257
+
<aid="-2134375864"></a>**Sync needs to reconcile the server and Azure file share data before files can be uploaded.**
Run the following PowerShell command on the server to reset the certificate: `Reset-AzStorageSyncServerCertificate -ResourceGroupName <string> -StorageSyncServiceName <string>`
1289
+
1229
1290
### Common troubleshooting steps
1230
1291
<aid="troubleshoot-storage-account"></a>**Verify the storage account exists.**
0 commit comments