Skip to content

Commit 013e178

Browse files
committed
AB#3426, AB#3425: Post Edit for two PRs
1 parent 74d2a66 commit 013e178

File tree

4 files changed

+11
-11
lines changed

4 files changed

+11
-11
lines changed

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-cloud-tiering.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Troubleshoot common issues with cloud tiering in an Azure File Sync
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: troubleshooting
7-
ms.date: 10/24/2024
7+
ms.date: 01/13/2025
88
ms.author: kendownie
99
ms.reviewer: vritikanaik, v-weizhu
1010
ms.custom: sap:File Sync
@@ -103,7 +103,7 @@ If content doesn't exist for the error code, follow the general troubleshooting
103103
| 0x800703e3 | -2147023901 | ERROR_OPERATION_ABORTED | The file failed to tier because it was recalled at the same time. | No action required. The file will be tiered when the recall completes and the file is no longer in use. |
104104
| 0x80c80264 | -2134375836 | ECS_E_GHOSTING_FILE_NOT_SYNCED | The file failed to tier because it hasn't synced to the Azure file share. | No action required. The file will tier once it has synced to the Azure file share. |
105105
| 0x80070001 | -2147942401 | ERROR_INVALID_FUNCTION | The file failed to tier because the cloud tiering filter driver (*storagesync.sys*) isn't running. | To resolve this issue, open an elevated command prompt and run the following command: `fltmc load storagesync`<br/>If the Azure File Sync filter driver fails to load when running the `fltmc` command, uninstall the Azure File Sync agent, restart the server, and reinstall the Azure File Sync agent. |
106-
| 0x80c86041 | -2134351807 | ECS_E_AFS_FILTER_NOT_LOADED | The file failed to tier because the cloud tiering filter driver (*storagesync.sys*) isn't running. | To resolve this issue, open an elevated command prompt and run the following command: `fltmc load storagesync`<br/>If the Azure File Sync filter driver fails to load when running the `fltmc` command, uninstall the Azure File Sync agent, restart the server, and reinstall the Azure File Sync agent. |
106+
| 0x80c86041 | -2134351807 | ECS_E_AFS_FILTER_NOT_LOADED | The file failed to tier because the cloud tiering filter driver (*storagesync.sys*) isn't running. | To resolve this issue, open an elevated command prompt and run this command `fltmc load storagesync`. <br/>If the Azure File Sync filter driver fails to load when running the `fltmc` command, uninstall the Azure File Sync agent, restart the server, and reinstall the Azure File Sync agent. |
107107
| 0x80070070 | -2147024784 | ERROR_DISK_FULL | The file failed to tier due to insufficient disk space on the volume where the server endpoint is located. | To resolve this issue, free at least 100 MiB of disk space on the volume where the server endpoint is located. |
108108
| 0x80070490 | -2147023728 | ERROR_NOT_FOUND | The file failed to tier because it hasn't synced to the Azure file share. | No action required. The file will tier once it has synced to the Azure file share. |
109109
| 0x80c80262 | -2134375838 | ECS_E_GHOSTING_UNSUPPORTED_RP | The file failed to tier because it's an unsupported reparse point. | If the file is a Data Deduplication reparse point, follow the steps in the [planning guide](/azure/storage/file-sync/file-sync-planning#data-deduplication) to enable Data Deduplication support. Files with reparse points other than Data Deduplication aren't supported and won't be tiered. |

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Troubleshoot common issues with installing the Azure File Sync agen
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: troubleshooting
7-
ms.date: 01/03/2025
7+
ms.date: 01/13/2025
88
ms.author: kendownie
99
ms.custom: sap:File Sync
1010
---
@@ -67,9 +67,9 @@ MSI (s) (0C:C8) [12:23:40:994]: Note: 1: 2265 2: 3: -2147287035
6767

6868
For this example, the agent installation failed with error code -2147287035 (ERROR_ACCESS_DENIED).
6969

70-
<a id="agent-installation-gpo"></a>**Agent installation fails with error: ERROR_NO_SYSTEM_RESOURCES with Error Code 0x800705AA**
70+
<a id="agent-installation-gpo"></a>**Agent installation fails with error ERROR_NO_SYSTEM_RESOURCES and error code 0x800705AA**
7171

72-
The agent installation failed due to insufficient system resources. To resolve this issue, please free up memory on the server and retry installation.
72+
The agent installation failed due to insufficient system resources. To resolve this issue, free up memory on the server and retry installation.
7373

7474

7575
<a id="agent-installation-gpo"></a>**Agent installation fails with error: Storage Sync Agent Setup Wizard ended prematurely because of an error**

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Troubleshoot common issues in managing Azure File Sync sync groups,
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: troubleshooting
7-
ms.date: 12/16/2024
7+
ms.date: 01/13/2025
88
ms.author: kendownie
99
ms.reviewer: v-weizhu
1010
ms.custom: sap:File Sync
@@ -100,7 +100,7 @@ This error occurs because Azure File Sync doesn't support server endpoints on vo
100100
compact /u /s
101101
```
102102

103-
<a id="-2134376345"></a>**Server endpoint creation fails, with this error message: "The server endpoints per server limit has been reached" (Error code: -2134376345 or 0x80C80067)**
103+
<a id="-2134376345"></a>**Server endpoint creation fails with this error message: "The server endpoints per server limit has been reached" (Error code: -2134376345 or 0x80C80067)**
104104

105105
This error occurs if the limit of server endpoints per server is reached. Azure File Sync currently supports up to 30 server endpoints per server. For more information, see
106106
[Azure File Sync scale targets](/azure/storage/files/storage-files-scale-targets?toc=/azure/storage/filesync/toc.json#azure-file-sync-scale-targets).

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Troubleshoot common issues that you might encounter with Azure File
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: troubleshooting
7-
ms.date: 08/01/2024
7+
ms.date: 01/13/2025
88
ms.author: kendownie
99
ms.custom: sap:File Sync
1010
---
@@ -97,16 +97,16 @@ After installing or upgrading the Azure File Sync agent (v17.3 or later), you ma
9797
Error 0x80070057: The parameter is incorrect.
9898
```
9999
100-
- Registering a server using the Register-AzStorageSyncServer cmdlet fails with the following error:
100+
- Registering a server using the `Register-AzStorageSyncServer` cmdlet fails with the following error:
101101
102102
```
103103
Register-AzStorageSyncServer: Exception of type 'Commands.StorageSync.Interop.Exceptions.ServerRegistrationException' was thrown.
104104
```
105105
106106
- ServerRegistration.exe or AfsUpdater.exe fails to open
107-
- Agent installation fails and installation log shows error code 0x80c84111 with message:
107+
- Agent installation fails. The installation log shows the error code 0x80c84111 with the following message:
108108
109-
```
109+
```output
110110
Exception occurred while configuring MitigationRedirection policy. This could indicate that required windows updates not installed on the computer.
111111
```
112112

0 commit comments

Comments
 (0)