Sharon provides a high-level overview of the various Azure File Sync errors and fix that can be used to troubleshoot sync file issues.
- [Instructor] For the exam you'll be required to know some Azure File Sync troubleshooting techniques. And the first technique is knowing what not to do. You do not want to remove the server endpoint if you're having sync errors, as this could result in a loss of data. Other general troubleshooting techniques include reviewing the operational and diagnostic logs for the sync service. You'll need to verify that the Azure File Sync service is running on the server.
You'll need to verify that the Azure File Sync filter drivers are also running on the server, and those drivers are StorageSync.sys and StorageSyncGuard.sys. And finally you'll need to run the AFSDiag tool and review the output to help you diagnose and troubleshoot sync errors. Now that we understand the basic troubleshooting techniques, let's go ahead and take a look at some of the detailed error messages. And we'll start off with registration errors.
If you're trying to register your server and the error pops up the term find-AzureRmResource is not recognized as the name during registration, this is because the cmdlet was changed in AzureRM v six. Therefore, you need to install Module AzureRM 5.7.0. I would highly recommend that on your server that you install the latest AzureRM modules. There are several things that can go wrong when you're install the agent on the server.
The first thing you need to do if you run into installation failures installing the agent is review the installer log by running StorageSyncAgent.msi/l*v Installer.log. You can then view that log to help you diagnose the issue. Another common setup that will produce an agent installation failure is if you have Microsoft Update enabled on the server but the Windows Update service is not running. With that combination the agent will fail.
If you're installing the agent on a domain controller and it fails it could be because you're on server 2008 R2 or below. If that is the situation you'll need to move the PDC role from the domain controller to a domain controller that is running Server 2012 R2 and above. If you encounter the error Storage Sync Agent Wizard while installing the agent it's because you're using the older version of the agent.
As always, be sure to download the most current version of the agent from the documentation website. I cannot stress that enough as this is still in preview and it will change. And our final agent installation failure is the server is not listed under the registered servers. So you may have gone ahead and set this up but it's not going to be listed. In that case you need to reset the Storage Sync Server. You may also run into errors in the Sync Group configuration.
Probably the most common one you'll run into is the specified Azure FileShare is already in use by a different CloudEndpoint. And that's pretty self explanatory. That Azure FileShare is already in use somewhere else. If you're creating an endpoint and it fails with AuthorizationFailed it's because user account does not have the correct permissions. The user who is creating these endpoints must have the following read permissions: Get role definition and get role assignment. And the following write permissions: Create or update custom role definition and create role assignments.
You may want to refer to the documentation to determine which built-in roles already have these rights assigned to them. Next we're gonna move on to issues you may encounter on the server. An error you may see is management server job failed with a code number. If you see this it's because you have cloud tiering enabled on your server endpoint path that happens to be on a system volume. This configuration is not supported. If the path is on a system volume then you're going to need to disable cloud tiering.
You may also encounter the error, MgmtServerJobExpired. In this case your server is offline or it's unreachable. Check your networking. Now we'll move into some sync issues. If the sync fails on the server you need to verify the endpoints that exist in Azure and again review those operational and diagnostic event logs. And our next error, the replica is not ready to perform the required operation is probably going to be seen a number of times.
And that's just because we tend to be inpatient. You will see this error while the data is initially syncing. And along those lines remember the Azure FileShare, so the data in Azure, will only sync down to our server shares every 24 hours. Another sync error that you may encounter is the storage account name used could not be resolved. If you come across this error you'll need to verify that you can resolve the storage DNS name and verify that the hybrid file sync service has been assigned to the reader and data access rule.
The error, this PC doesn't have enough free space indicates that you have less than one gig of free space on that volume. Therefore, you're going to need to increase the size of the volume. On occasion you may come across errors in cloud storage. A common error could be the Azure FileShare is inaccessible. And this is typically because the Azure FileShare was deleted but is still associated with a cloud endpoint. The Azure storage account may also become inaccessible.
If that happens it's because a storage account was deleted, but it is still associated with the Azure FileShare. And finally, a couple of errors if you're going to configure cloud tiering. A common error is the Azure File Sync file system filter, that StorageSync.sys is not loaded. In that case all you need to do is reload that filter. You may encounter missing, corrupt, or broken reparse points when using cloud tiering.
And this is caused because someone has modified the tagger data. And finally if you come across an issue dealing with network connectivity issues, your resolution is to verify that the server has internet connectivity. This has been a fairly high level overview of some of the troubleshooting techniques for Azure File Sync. Before writing the exam I would highly recommend that you review this documentation as it may change because this service is still in preview.
- Managing Azure subscriptions and resources
- Implementing and managing storage
- Configuring and managing virtual networks
- Managing identities
- Evaluating and performing server migration to Azure
- Implementing and managing application services
- Implementing advanced virtual networking
- Securing identities