Forum Discussion
Onedrive (NGSC Preview) keeps processing changes, but doesn't process several files
- Jan 19, 2017
Just letting everyone know that Microsoft have now told me that this is a backend issue and you can now monitor the progress updates in the Sharepoint Admin portal, as it is showing as degraded. See below
Office Admin center - Service health
SP90878 - SharePoint Features - Restoring serviceRestoring service - 19 Jan 2017 7:21 a.m.Title: Next Generation Sync Client issueUser Impact: Users may be unable to sync their team site files using the Next Generation Sync Client (OneDrive.exe).More info: Affected users may observe that the sync client is in a persistent state of "processing changes" when syncing SharePoint team sites. The folder structure is correctly updated; however, the files themselves may not sync correctly.Current status: The deployment of the fix is now in progress and is expected to reach the majority of affected systems within 24 hours. Users will begin to experience service restoration as the fix propagates throughout the environment.Scope of impact: A few customers have reported this issue, and our analysis indicates that this issue may potentially affect any of your users attempting to sync team sites. This issue only affects the OneDrive.exe client. The Groove.exe client is unaffected.Start time: Tuesday, January 17, 2017, at 2:12 PM UTCPreliminary root cause: An update intended to resolve a previously existing issue with processing incoming service requests inadvertently impacted the ability to sync team sites.Next update by: Thursday, January 19, 2017, at 7:00 PM UTC
SP90878 has now been 'rectified' - however my team is still having issues with no files being downloaded from any of our libraries. Is anyone else still having issues?
Uninstalled and reinstalled NGSC multiple times on multiple OS's. Still stuck with 0.0 KB downloaded.
Hi David we are also experiening the same issue with one of our clients whilst others are now working fine, I have raised another support ticket with Microsoft, as although they claim it is now resolved this is obviouly not the case for everyone. I'd recommend that you also raise a support ticket yourself. I'll post any updates here once I have any further information. I'm currently waiting on a call back from Microsoft.