Forum Discussion
Sync button on channel not working anymore
Hi,
i (and many other colleagues) experiencing a problem with the sync button within the Teams channel.
I can click on it - but nothing will happen.
- There is no special sign in the display name
- The library itself is not synced
- Newest windows updates installed
- on the sharepoint site it works
Version OneDrive is
20.134.705.8
Version Teams is
1.3.00.21759
Version Windows is
1909
Anyone else has these problems? I did not start Fiddler yet
best regards
Stephan
StephanGee had the same problem.... if you open the lib in Sharepoint the Sync button works there.
63 Replies
- Mark-Kashman
Microsoft
Hi StephanGee et al.
Per word from my engineering team, all necessary fixes have been released.
Please let me know if you are still seeing this issue. And if so, please send a quick list of actions you've taken to repro the issue. In my own two tests, I was able to sync properly from Teams today (Jan.19.2021).
Thanks, Mark
- StephanGeeSteel Contributor
Hi Mark.
I get one step further but it did not sync. It stays at this point. The same problem is showing up for some of my colleagues.
OneDrive Version
After signing out and in in Teams it worked.
- Luke HoffmanIron Contributor
StephanGee Mark-Kashman We have the exact same issue. Users are really frustrated with the Teams client. The amount of times they are told to sign out and back in for various reasons in crazy. There needs to be a better answer. This may be a known bug, but it's still not fixed it's only changed its behavior. Instead of nothing happen this dialogue pops up and then nothing happens.
- halbpCopper Contributor
Mark-Kashman This fix has actually made my problem worse. Now when I click on the sync button, the onedrive client crashes.
Edit: in fact it won't run at all now, it crashes 10 seconds after launching. Managed to at least get it running again using %localappdata%\Microsoft\OneDrive\onedrive.exe /reset...
Version: 1.3.00.30866 (64-bit), no more updates found.
This issue has been the single biggest blocker to Teams adoption in our company, we're trying to roll it out, users want to use file explorer, and the sync button has been broken for months. It's embarrassing, and we have to tell the users that it is broken, open in SharePoint etc.
Please sort this out.
- Mark-Kashman
Microsoft
I will share your note with our engineers to see if this is known and anything we can do to help. Is this an isolated experience you are seeing, or also systemic to anyone you're working with at your company in preparation to broader roll out. If you have additional repo instances, that is good to know if they are the same experience or not. Helps drill into the problem.
- aljimferCopper Contributor
Hi Mark-Kashman et al.
I've been having this issue for months. After reading your last message I've logged out, re-started Teams and logged in again and I'm happy to say that the issue has dissapeared for me.
Thank you
- Mark-Kashman
Microsoft
Great to hear. Grateful for your patience.
- sliebenbergCopper ContributorHi, has this issue been fixed ? Still experiencing this problem with Teams version 1.3.00.28779
- Barbara_Hoegen_DijkhofCopper ContributorHi, The weirdest thing is that last week the sync button worked.. I checked this myself. But when I check know we have the same issue as before. I am working on version 1.3.00.28779 as well. It was last updated on 10/30/20. So i don't know what going on. A client told me the button was working again but they are working on the version before 28779.
- PsychoDataCopper Contributoras far as I can tell, it is the Teams updates.
Because reinstalling Teams has always temporarily fixed the issue for me - so when Teams goes through it's normal Auto-update process, it "randomly" fixes it again
Then eventually breaks
But gets "fixed" again when the next update comes out!
Repeat until patch stops it breaking again
- PsychoDataCopper Contributor
sliebenberg Microsoft told several of us, me included, that the fix was targeted to rollout around mid-December
- Mark-Kashman
Microsoft
StephanGee - I received this update from my OneDrive and Teams engineering colleagues regarding this issue: "This is a known issue and the fix is in progress. This update should begin to release to the production environment early in December 2020." I will take a note to ping back on this thread to note when the fix begin rolling out. - Mark Kashman
- Nicolò ManzottiIron Contributor
Mark-Kashman any updates on this?
It's early January and, unfortunately, we are still facing the issue on both Windows 10 and macOS.
MacOs Teams client version: 1.3.00.28778 (it says it was last updated 2020/11/19, so I guess the version fixing this might have not been released to everyone yet).
- PsychoDataCopper Contributor
I had opened a ticket with Microsoft support and got the same word about this being related to a known bug.
After I finally put my foot down and told them to stop suggesting I keep reinstalling Teams for a 4th or 5th time and that I KNOW that fixes it temporarily, but it keeps doing it again.
Only took something like 4 hours of wasted time on the phone with support, and requesting a different tech/escalating the issue a couple times when they kept suggesting I ignore the problem by reinstalling, for them to finally look at the issue
- Barbara_Hoegen_DijkhofCopper ContributorThis is very helpfull. Thank you very much!
- Mark-Kashman
Microsoft
StephanGee Thanks for calling this to attention. Looping in Miceile Barrett and Sreeram Ramamoorthy for awareness, plus I'll kick off an internal chat on same.
For the immediate work around when you hit this issue, please navigate to the connected SharePoint team site (where the content is stored) and click the "Sync" button when you are on the document library or specific folder you want to sync; related help article: https://support.microsoft.com/office/sync-sharepoint-and-teams-files-with-your-computer-6de9ede8-5b6e-4503-80b2-6190f3354a88
- Mark Kashman (SharePoint product manager)
- Erol-ECopper Contributor
Mark-Kashman Wanted you to understand, this issue has been observed for several months in several different tenant accounts. We find Asking folks to use this workaround is a bit embarrassing, and serves only to destroy everyone's credibility and the product's integrity, as the issue drags on with no end in sight. Also, coincidentally and perhaps Not, in the same Tenants we have started to observe when attempting to configure New Retention Management Policies for OneDrive and SharePoint Sites, the Policies fail to deploy. We seem to receive a consistent error message with a Distribution Result found saying, "Policy cannot be deployed to the content source due to a temporary Office 365 datacenter issue. The current policy is not applied to any content in the source, so there's no impact from the blocked deployment. To fix this issue, please try redeploying the policy." Deleting and Recreating the Policy, Attempting to Restart Policy Propagation, Deploy with PowerShell, etc. have shown no success.
- NormPollockCopper Contributor
Sync was not working on 2 machines for me, but logging out of Teams and back in corrected the issue immediately.
- SC-BPCCopper Contributor
The solution to sign-out of OneDrive and Teams, then restart the computer only works temporarily for me.
I don't sync folders very often, but just about every time I have to sync a folder (every other month or so), I have to sign-out of the apps and restart the computer. It works for a while, but the next time I have to sync a folder, which could be within weeks to months, it stops working again, so I have to do it all over again.
- TTAdminCopper Contributor
SC-BPC - hmmm yep sure enough, my sync button has again stopped working. This time, as NormPollock suggests, logging out (and quitting Teams, then reloading) and logging back in again corrected it.
I really hope MS fixes this soon.
- AXS_PrimeCopper Contributor
StephanGeeSame here.
I opened a ticket with Microsoft. They walk through the workaround and do not get to a fix. This is now my pain in the neck for the past month. Clients call, I attempt to talk them through the workaround, though I usually end up having to remote to show them how to do it. They then get frustrated after several times that this fails and call me to make a stink. I point to the ticket that I refuse to close until there is a FIX(!!!). They let it ride for a few more days and then come again. Yeah, I'm sick of the workaround nonsense - patch it, Microsoft!
- Barbara_Hoegen_DijkhofCopper ContributorHi,
I experienced the same issue at our side as well as on customers side. As you mentioned this ''workaround'' is nonsense and not really an aswer to your customers. I am curious what MS replied as an fix for your ticket? Or is it stil open..- From what I have gathered, there is a fix in the testing pipeline for this issue, no ETA on actual release.
- RobSaddlerCopper Contributor
Erol-E Same here... it has affected almost all our userbase (~15-20) so small numbers but high percentage affected. I've also raised a ticket and been given the same workarounds. Logging out/in works for a day or so then the Teams button fails again so users are now opening in SharePoint. This has opened another world of pain as up until this point, users were ignorant of SharePoint as they did everything through Teams and now they are confused as hell about 'what this SharePoint thing is'. And let's be honest, there is no explanation that works for anyone other than a techie!
- FabioBielliIron Contributor
In my company we are still experimenting the problem, but I can't say how many users are involved. On my side I tried to enable and disable developer mode solving.
- GCDwaincCopper Contributor
We are running into this issue with some of our users now also. I agree that some of the work arounds mentioned are not a fix for end users
- DrewGrgichCopper Contributor
Same issue here. Signing out and back in to clear cache doesn't enable the sync function. At least I'm apparently not alone.
- DrewGrgichCopper Contributor
So in my case, the issue turned out to be trouble getting Windows Updates. My Windows Update service had been disabled and I haven't received updates in a couple of months. Fixing this and running a full update cycle fixed the issue.