Forum Discussion
A request for help: SharePoint causing tons of sync problems?
Seeing your NGSC version, I guess that you are also on Windows Insider.
Of course, I cannot say if the issues you are experiencing are actually due to installing Insider builds, but, in general, Insider (aka beta) versions of both Windows and Office should be avoided on production machines.
Also, instead of reusing existing Office documents, you should use Office templates. See for example http://www.techadvisory.org/2014/01/using-office-templates/
Finally, you could disable Autosave completely or only for single files. See https://support.office.com/en-us/article/what-is-autosave-6d6bd723-ebfd-4e40-b5f6-ae6e8088f7a5
Hope it helps...
- In order to disable permanently Autosave, follow this article: https://support.microsoft.com/en-us/help/4036334/how-to-disable-autosave-in-office-365-proplus. But don't do it if you are not comfortable with editing the registry! Anyway, you should consider using Office templates, instead of reusing existing files.
- OneDrive client insider builds are normally distributed together with Windows Insider builds... Have you tried to uninstall your build and subsequently download and install the latest production build? See https://support.office.com/en-gb/article/New-OneDrive-sync-client-release-notes-845dcf18-f921-435e-bf28-4e24b95e5fc0?ui=en-US&rs=en-GB&ad=GB
- Which Office version are you running? Is it connected with the issue discussed in the following thread? https://techcommunity.microsoft.com/t5/Outlook/Modern-Attachments-Cannot-set-perms/m-p/143931#M1353
Hi Salvatore,
I just want to say I appreciate you taking the time to help me. This has been a frustrating experience for a few months now, and I am happy to have some new things to try.
1. Thanks for the info on turning off autosave in the registry. I agree it isn't the best long term solution, but it can hopefully be a temporary way to save us from ourselves, especially until we can get some of the other features working properly.
2. Yesterday I uninstalled my build and reinstalled, but I used the download link found at the below link, which was the first place I was able to find a link to the client install.
https://support.office.com/en-us/article/Deploy-the-new-OneDrive-sync-client-in-an-enterprise-environment-3f3a511c-30c6-404a-98bf-76f95c519668
I have downloaded the install from the production link you provided, and will try to install later today.
3. Office automatically downloaded and installed a new version yesterday, and I am now showing 1803 (Build 9120.2015 click to run)
As far as I can tell, my issues are not related to the thread you linked to. These are the steps I take to reproduce my issue:
1. Create a new message in Outlook
2. Click the Attach file paperclip and select any item in the recent list that has a cloud icon over the file.
3. I get a pop-up asking me if I want to "Share Link" or "Attach as Copy" either selection I make I get a "Cannot find this file. Verify the path and filename are correct" error message. There is no problem with the non-cloud option of the same file stored in the same location.
Two developments as of this morning:
1) I was able to successfully attach a link to a cloud file from my education Office 365 account, but still cannot from my work account. Previously I've mostly been unable to attach from both accounts (but there have been occassional one off exceptions, so this might just be one of those. Will need to do more testing to be sure, once I've verified that I've installed the production client and got everything synced again.
2) Yesterday I reported that the "browse web locations" option was missing from the attach files dropdown in Outlook. That is now back. My guess is that afte rI uninstalled the OneDrive client, it took sometime for everything to resync before that option showed up again.
3) The same thing is true of the Share option in Office, that is back and seems to work normally again and the links work.
You can force the channel switch (if the channel is not configured by GPO). See https://blogs.technet.microsoft.com/odsupport/2017/05/10/how-to-switch-channels-for-office-2016-proplus/
You are right, it does still say Office Insider below the version number, something I had missed before. Above that I'm given the option to join Office Insider, so I think what will happen is whenever the next production build is released I will upgrade to that one, and then be on the production channel?
I understand that this is not guaranteed to fix my problems, and indeed I think it is unlikely that it will. I've had these problems from the moment I started using OneDrive on a new PC, which was at least a couple of months before I joined the Office Insider. Maybe I'll have more luck with the production build of OneDrive, since I've probably inadvertently been on the insider build for that product since I first installed it.
The link to the production build of the OneDrive client is the following (at the moment): https://go.microsoft.com/fwlink/?linkid=844652
The latest release of Office for non-insider channels is 1802 (9029.2167). See https://support.office.com/en-us/article/version-and-build-numbers-of-update-channel-releases-ae942449-1fca-4484-898b-a933ea23def7?ui=en-US&rs=en-US&ad=US
Hence I guess you are still in Office Insider. What do you read in the backstage under the version number?
Once again, I want to repeat that returning your setup to production builds is not a guarantee that your problems will be solved, but at least you should be in a more stable situation...