File sync problems

To resolve this issue, temporarily disable the Turn on Script Execution group policy setting on the server. Once the agent installation completes, the group policy setting can be re-enabled. Agent installation fails on Active Directory Domain Controller If you try to install the sync agent on an Active Directory domain controller where the PDC role owner is on a Windows Server R2 or below OS version, you may hit the issue where the sync agent will fail to install. To resolve, transfer the PDC role to another domain controller running Windows Server R2 or more recent, then install sync.

Accessing a volume on Windows Server R2 fails with error: The parameter is incorrect After creating a server endpoint on Windows Server R2, the following error occurs when accessing the volume:. To resolve this issue, install KB and restart the server. If this update will not install because a later update is already installed, go to Windows Update, install the latest updates for Windows Server R2 and restart the server.

This issue occurs because ServerRegistration. You can also work around this issue by using the following PowerShell commands to register the server:. Server Registration displays the following message: "This server is already registered". This message appears if the server was previously registered with a Storage Sync Service. To unregister the server from the current Storage Sync Service and then register with a new Storage Sync Service, complete the steps that are described in Unregister a server with Azure File Sync.

If the server is not listed under Registered servers in the Storage Sync Service, on the server that you want to unregister, run the following PowerShell commands:. If the server is part of a cluster, you can use the optional Reset-StorageSyncServer -CleanClusterRegistration parameter to also remove the cluster registration.

When I register a server, I see numerous "web site not trusted" responses. This issue occurs when the Enhanced Internet Explorer Security policy is enabled during server registration.

Server is not listed under registered servers in the Azure portal If a server is not listed under Registered servers for a Storage Sync Service:. Cloud endpoint creation fails, with this error: "The specified Azure FileShare is already in use by a different CloudEndpoint" This error occurs if the Azure file share is already in use by another cloud endpoint. If you see this message and the Azure file share currently is not in use by a cloud endpoint, complete the following steps to clear the Azure File Sync metadata on the Azure file share:.

Deleting the metadata on an Azure file share that is currently in use by a cloud endpoint causes Azure File Sync operations to fail. If you then use this file share for sync in a different sync group, data loss for files in the old sync group is almost certain. Cloud endpoint creation fails, with this error: "AuthorizationFailed" This error occurs if your user account doesn't have sufficient rights to create a cloud endpoint.

To create a cloud endpoint, your user account must have the following Microsoft Authorization permissions:. Server endpoint creation fails, with this error: "MgmtServerJobFailed" Error code: or 0x80c This error occurs if the server endpoint path is on the system volume and cloud tiering is enabled. Cloud tiering is not supported on the system volume.

To create a server endpoint on the system volume, disable cloud tiering when creating the server endpoint. Server endpoint creation fails, with this error: "MgmtServerJobFailed" Error code: or 0x This error occurs if the server endpoint path specified is not valid. Verify the server endpoint path specified is a locally attached NTFS volume. Note, Azure File Sync does not support mapped drives as a server endpoint path.

Server endpoint creation fails, with this error: "MgmtServerJobFailed" Error code: or 0x80c This error occurs if the server endpoint path specified is not an NTFS volume. Server endpoint creation fails, with this error: "MgmtServerJobFailed" Error code: or 0x80cd This error occurs because Azure File Sync does not support server endpoints on volumes, which have a compressed System Volume Information folder.

To resolve this issue, decompress the System Volume Information folder. If the System Volume Information folder is the only folder compressed on the volume, perform the following steps:. Server endpoint creation fails, with this error: "MgmtServerJobFailed" Error code: or 0x80C 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 Azure File Sync scale targets. Server endpoint creation fails, with this error: "MgmtServerJobFailed" Error code: or 0x80c This error occurs if another server endpoint is already syncing the server endpoint path specified.

Azure File Sync does not support multiple server endpoints syncing the same directory or volume. Server endpoint creation fails, with this error: "MgmtServerJobFailed" Error code: or 0x80c This error occurs if the server endpoint path contains orphaned tiered files.

If a server endpoint was recently removed, wait until the orphaned tiered files cleanup has completed. An Event ID is logged to the Telemetry event log once the orphaned tiered files cleanup has started. An Event ID is logged once the orphaned tiered files cleanup has completed and a server endpoint can be recreated using the path. If the server endpoint creation fails after the tiered files cleanup has completed or if Event ID cannot be found in the Telemetry event log due to event log rollover, remove the orphaned tiered files by performing the steps documented in the Tiered files are not accessible on the server after deleting a server endpoint section.

Server endpoint deletion fails, with this error: "MgmtServerJobExpired" Error code: or 0x80c This error occurs if the server is offline or doesn't have network connectivity. If the server is no longer available, unregister the server in the portal, which will delete the server endpoints. To delete the server endpoints, follow the steps that are described in Unregister a server with Azure File Sync.

Unable to open server endpoint properties page or update cloud tiering policy This issue can occur if a management operation on the server endpoint fails. If the server endpoint properties page does not open in the Azure portal, updating server endpoint using PowerShell commands from the server may fix this issue.

Server endpoint has a health status of "No Activity" or "Pending" and the server state on the registered servers blade is "Appears offline". If GetNextJob completed with status: is logged, the server is unable to communicate with the Azure File Sync service due to a firewall, proxy, or TLS cipher suite order configuration. If the server is behind a firewall, verify port outbound is allowed.

If the firewall restricts traffic to specific domains, confirm the domains listed in the Firewall documentation are accessible. If the server is behind a proxy, configure the machine-wide or app-specific proxy settings by following the steps in the Proxy documentation. Use the Test-StorageSyncNetworkConnectivity cmdlet to check network connectivity to the service endpoints.

To learn more, see Test network connectivity to service endpoints. If the TLS cipher suite order is configured on the server, you can use group policy or TLS cmdlets to add cipher suites:. If GetNextJob completed with status: is logged, the server is unable to communicate with the Azure File Sync service due to an expired or deleted certificate. Server endpoint has a health status of "No Activity" and the server state on the registered servers blade is "Online".

A server endpoint health status of "No Activity" means the server endpoint has not logged sync activity in the past two hours. To check current sync activity on a server, see How do I monitor the progress of a current sync session? A server endpoint may not log sync activity for several hours due to a bug or insufficient system resources.

Verify the latest Azure File Sync agent version is installed. If the issue persists, open a support request. If the server state on the registered servers blade is "Appears Offline," perform the steps documented in the Server endpoint has a health status of "No Activity" or "Pending" and the server state on the registered servers blade is "Appears offline" section.

If I created a file directly in my Azure file share over SMB or through the portal, how long does it take for the file to sync to servers in the sync group? Changes made to the Azure file share by using the Azure portal or SMB are not immediately detected and replicated like changes to the server endpoint. Azure Files does not yet have change notifications or journaling, so there's no way to automatically initiate a sync session when files are changed.

To detect changes to the Azure file share, Azure File Sync has a scheduled job called a change detection job. A change detection job enumerates every file in the file share, and then compares it to the sync version for that file.

When the change detection job determines that files have changed, Azure File Sync initiates a sync session. The change detection job is initiated every 24 hours. Because the change detection job works by enumerating every file in the Azure file share, change detection takes longer in larger namespaces than in smaller namespaces. For large namespaces, it might take longer than once every 24 hours to determine which files have changed.

To immediately sync files that are changed in the Azure file share, the Invoke-AzStorageSyncChangeDetection PowerShell cmdlet can be used to manually initiate the detection of changes in the Azure file share. This cmdlet is intended for scenarios where some type of automated process is making changes in the Azure file share or the changes are done by an administrator like moving files and directories into the share. This way all changes will quickly sync to other agents without the need to use the Invoke-AzStorageSyncChangeDetection cmdlet.

Help us prioritize this feature for future development by voting for it at Azure Community Feedback. Server endpoint health is in a pending state for several hours This issue is expected if you create a cloud endpoint and use an Azure file share that contains data. The change enumeration job that scans for changes in the Azure file share must complete before files can sync between the cloud and server endpoints.

The time to complete the job is dependent on the size of the namespace in the Azure file share. The server endpoint health should update once the change enumeration job completes. Within each sync group, you can drill down into its individual server endpoints to see the status of the last completed sync sessions.

A green Health column and a Files Not Syncing value of 0 indicate that sync is working as expected. If not, see below for a list of common sync errors and how to handle files that are not syncing. Event corresponds to a completed sync session; for the latest status of sync, look for the most recent event with ID SyncDirection tells you if this session was an upload or download. If the HResult is 0, then the sync session was successful.

A non-zero HResult means that there was an error during sync; see below for a list of common errors. If the PerItemErrorCount is greater than 0, then some files or folders did not sync properly. Below is an example of a successful upload. For the sake of brevity, only some of the values contained in each event are listed below. Sometimes sync sessions fail overall or have a non-zero PerItemErrorCount but still make forward progress, with some files syncing successfully.

These fields describe how much of the session is succeeding. If you see multiple sync sessions in a row that are failing but have an increasing Applied count, then you should give sync time to try again before opening a support ticket. Within your sync group, go to the server endpoint in question and look at the Sync Activity section to see the count of files uploaded or downloaded in the current sync session.

Keep in mind that this status will be delayed by about 5 minutes, and if your sync session is small enough to be completed within this period, it may not be reported in the portal. This event indicates the state of the current sync session. TotalItemCount denotes how many files are to be synced, AppliedItemCount the number of files that have been synced so far, and PerItemErrorCount the number of files that are failing to sync see below for how to deal with this.

If you made changes directly in your Azure file share, Azure File Sync will not detect these changes until change enumeration runs, which happens once every 24 hours.

It is possible that a server will say it is up to date with the cloud when it is in fact missing recent changes made directly in the Azure file share. If your PerItemErrorCount on the server or Files Not Syncing count in the portal are greater than 0 for any given sync session, that means some items are failing to sync. Files and folders can have characteristics that prevent them from syncing.

These characteristics can be persistent and require explicit action to resume sync, for example removing unsupported characters from the file or folder name. They can also be transient, meaning the file or folder will automatically resume sync; for example, files with open handles will automatically resume sync when the file is closed. When the Azure File Sync engine detects such a problem, an error log is produced that can be parsed to list the items currently not syncing properly.

To see these errors, run the FileSyncErrorsReport. The ItemPath field tells you the location of the file in relation to the root sync directory. See the list of common sync errors below for remediation steps.

If the FileSyncErrorsReport. Cause 1: The last completed sync session did not have per-item errors. The portal should be updated soon to show 0 Files Not Syncing. By default, the FileSyncErrorsReport. To view per-item errors for all sync sessions, use the -ReportAllErrors parameter. Cause 2: The ItemResults event log on the server wrapped due to too many per-item errors and the event log no longer contains errors for this sync group.

PowerShell will likely print these characters as question marks or empty rectangles since most of these characters have no standard visual encoding. The Evaluation Tool can be used to identify characters that are not supported. If your dataset has several files with invalid characters, use the ScanUnsupportedChars script to rename files which contain unsupported characters.

Sync sessions may fail for various reasons including the server being restarted or updated, VSS snapshots, etc. Although this error looks like it requires follow-up, it is safe to ignore this error unless it persists over a period of several hours. This error can occur whenever the Azure File Sync service is inaccessible from the server. You can troubleshoot this error by working through the following steps:. Verify that port is open to outgoing connections to the Azure File Sync service.

You can do this with the Test-NetConnection cmdlet. Ensure that the proxy configuration is set as anticipated. More information on configuring the proxy configuration for Azure File Sync can be found in the Azure File Sync proxy and firewall settings. Contact your network administrator for additional assistance troubleshooting network connectivity.

Once network connectivity to the Azure File Sync service is restored, sync may 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. No action is required; the server will try again. If this error persists for several hours, create a support request. Sync is blocked until change detection completes post restore. No action is required.

When a file or file share cloud endpoint is restored using Azure Backup, sync is blocked until change detection completes on the Azure file share. Change detection runs immediately once the restore is complete and the duration is based on the number of files in the file share. This error typically occurs when a backup application creates a VSS snapshot and the sync database is unloaded.

Sync can't access the Azure file share specified in the cloud endpoint. This error occurs because the Azure File Sync agent cannot access the Azure file share, which may be because the Azure file share or the storage account hosting it no longer exists. Sync failed because the request is not authorized to perform this operation.

This error occurs because the Azure File Sync agent is not authorized to access the Azure file share. The storage account name used could not be resolved. Verify the storage account exists. Verify the firewall and virtual network settings on the storage account are configured properly if enabled. An unknown error occurred while accessing the storage account.

Step 1. Then open Sync Center. Input the regedit in Windows 7 search box, and press Enter. Then Reboot the computer the new key will delete itself after rebooting along with the Offline Files cache.

Sometimes, you might the the Offline files is enabled but not yet active. Rstart this computer to activate Offline Files. Step 3. Step 4. Enable Offline Files. And now, enable offline files greyed out, disable offline files greyed out and always available offline greyed out i n Windows 7 should be fixed.

Solution : Open the file by using an application that is not managed by Windows Information Protection. Or open the online files after connect the network. If you encounter the above same Windows sync center problems in Windows 10, please try the solutions respectively.

Input sync center in Windows search box, and press Enter. Select a conflict from the list. And click Resolve. Or right click the conflict, and choose View options to resolve Select the file version that you want to sync.

Meanwhile, the other versions of the data will be deleted automatically. Or else, you'll see the "This file is too big to upload" or "Reduce the size of the file to upload to" error messages. You can store OneNote notebooks in OneDrive, but the note-taking app uses a different sync process.

If you want to share a notebook, you should make it available to other users using the OneNote app. Otherwise, if you try to share the notebook using OneDrive, you'll come across syncing issues. If you're trying to move the OneDrive folder to another location, consider that the app doesn't support mapped drives or shared network folders.

As a result, sync won't work. Disabling or removing OneDrive in Windows 10 would be an easy job. This post will tell you how to disable or remove OneDrive with a few steps. That is all information about the OneDrive sync issues and this post provides some useful methods to fix them. If you think the methods are effective, share it on Twitter to let more people know. Click to tweet. Besides the sync feature, it also has a backup feature, which can help you to back up the disk, partition, files, folders and the operating system.

In addition, MiniTool ShadowMaker can also help you to clone the operating system from HDD to the SSD without data loss to improve the performance of your computer and reduce the program loading time. This backup software offers a Trial Edition that allows a day free trial for all backup features. You can download it. Free Download. Now, it is time to show you how to sync files. I will show you the tutorials with the step-by-step guide. Want to create automatic file backups in Windows 10?

This post shows you how to automatically back up files to an external hard drive with ease. You can click Sync Now to sync the files immediately. Or you can also click Sync Later to delay the file sync process. Then you can re-start this task in the Manage tab. When you have finished all the steps, you have successfully synchronized files to another location to keep your data safe.

MiniTool ShadowMaker is a piece of useful sync software that helps me to sync files and folders to keep my data safe, and it is very easy to operate. Here are 9 useful and powerful methods to fix OneDrive sync issues. For the question regarding MiniTool software, please tell us by contacting [email protected] or leaving a comment below. Download Shadowmaker.