Skip to content

Commit 9d9394b

Browse files
committed
Adding sync error codes part 4
1 parent e974c7d commit 9d9394b

File tree

1 file changed

+76
-15
lines changed

1 file changed

+76
-15
lines changed

articles/storage/file-sync/file-sync-troubleshoot-sync-errors.md

Lines changed: 76 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -175,6 +175,17 @@ The table below contains all of the unicode characters Azure File Sync does not
175175

176176
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.
177177

178+
<a id="-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+
178189
<a id="-2147012889"></a>**A connection with the service could not be established.**
179190

180191
| Error | Code |
@@ -205,6 +216,13 @@ Sync sessions might fail for various reasons including the server being restarte
205216
| **Error string** | UNEXPECTED_NETWORK_ERROR |
206217
| **Remediation required** | Yes |
207218

219+
| Error | Code |
220+
|-|-|
221+
| **HRESULT** | 0x80072ee2 |
222+
| **HRESULT (decimal)** | -2147012894 |
223+
| **Error string** | WININET_E_TIMEOUT |
224+
| **Remediation required** | Yes |
225+
208226
[!INCLUDE [storage-sync-files-bad-connection](../../../includes/storage-sync-files-bad-connection.md)]
209227

210228
> [!Note]
@@ -533,20 +551,6 @@ This error can happen if your organization is using a TLS terminating proxy or i
533551
534552
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.
535553
536-
<a id="-2147012894"></a>**A connection with the service could not be established.**
537-
538-
| Error | Code |
539-
|-|-|
540-
| **HRESULT** | 0x80072ee2 |
541-
| **HRESULT (decimal)** | -2147012894 |
542-
| **Error string** | WININET_E_TIMEOUT |
543-
| **Remediation required** | Yes |
544-
545-
[!INCLUDE [storage-sync-files-bad-connection](../../../includes/storage-sync-files-bad-connection.md)]
546-
547-
> [!Note]
548-
> 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-
550554
<a id="-2147012721"></a>**Sync failed because the server was unable to decode the response from the Azure File Sync service**
551555
552556
| Error | Code |
@@ -632,7 +636,9 @@ This error occurs because the server endpoint deletion failed and the endpoint i
632636
| **Error string** | ECS_E_NOT_ENOUGH_LOCAL_STORAGE |
633637
| **Remediation required** | Yes |
634638

635-
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.
636642

637643
<a id="-2134364145"></a><a id="replica-not-ready"></a>**The service isn't yet ready to sync with this server endpoint.**
638644

@@ -1226,6 +1232,61 @@ Check if the Azure file share exists in the storage account.
12261232

12271233
No action required. This error should automatically resolve. If the error persists for several days, create a support request.
12281234

1235+
<a id="-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.
1245+
1246+
<a id="-2134364007"></a>**Private endpoint configuration access blocked.**
1247+
1248+
| Error | Code |
1249+
|-|-|
1250+
| **HRESULT** | 0x80c83099 |
1251+
| **HRESULT (decimal)** | -2134364007 |
1252+
| **Error string** | ECS_E_PRIVATE_ENDPOINT_ACCESS_BLOCKED |
1253+
| **Remediation required** | Yes |
1254+
1255+
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+
<a id="-2134375864"></a>**Sync needs to reconcile the server and Azure file share data before files can be uploaded.**
1258+
1259+
| Error | Code |
1260+
|-|-|
1261+
| **HRESULT** | 0x80c80248 |
1262+
| **HRESULT (decimal)** | -2134375864 |
1263+
| **Error string** | ECS_E_REPLICA_RECONCILIATION_NEEDED |
1264+
| **Remediation required** | No |
1265+
1266+
No action required. This error should automatically resolve. If the error persists for several days, create a support request.
1267+
1268+
<a id="0x4c3"></a>**Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.**
1269+
1270+
| Error | Code |
1271+
|-|-|
1272+
| **HRESULT** | 0x4c3 |
1273+
| **HRESULT (decimal)** | N/A |
1274+
| **Error string** | ERROR_SESSION_CREDENTIAL_CONFLICT |
1275+
| **Remediation required** | Yes |
1276+
1277+
Disconnect all previous connections to the server or shared resource and try again.
1278+
1279+
<a id="-2134376368"></a>**The server's SSL certificate is invalid or expired.**
1280+
1281+
| Error | Code |
1282+
|-|-|
1283+
| **HRESULT** | 0x80c80050 |
1284+
| **HRESULT (decimal)** | -2134376368 |
1285+
| **Error string** | ECS_E_SERVER_INVALID_OR_EXPIRED_CERTIFICATE |
1286+
| **Remediation required** | Yes |
1287+
1288+
Run the following PowerShell command on the server to reset the certificate: `Reset-AzStorageSyncServerCertificate -ResourceGroupName <string> -StorageSyncServiceName <string>`
1289+
12291290
### Common troubleshooting steps
12301291
<a id="troubleshoot-storage-account"></a>**Verify the storage account exists.**
12311292
# [Portal](#tab/azure-portal)

0 commit comments

Comments
 (0)