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...
First of all, NGSC 18.025.0204.0009 is an Insider Ring build. Have you considered switching to Production Ring? Insider builds are unstable by their nature, so it is unsurprising to experience glitches and bugs.
Second, which Office version are you running? Are you in Office Insider too, perhaps?
So it will obviously take awhile before I can see if production builds fix any of my issues. While I'm waiting for that, any suggestions on how to roll back a couple of Word files to a previous version and keep the original modified date? As mentioned, clicking on enable editing gives me a generic file error. Copying the data into a new file will lose the modified date, which is pretty important for these files as we need to be able to see when certain changes have been made over multiple year stretches.
Since you are dependent on the modified date value, i would recommend adding a custom date field (as a site column) so that you could control that value, maybe called Issued Date, or something similar. this will help you in the future and help you to ensure that a date you depend on is something that you can control.
Thanks for the suggestion. So far we haven't used any of the features of SPO and have just used it as an online file storage with the ability to sync everything down to our individual computers. But I'll look into that and see if it might work for us.
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...
Thanks again for the input. I just double checked, and I'm not in the Windows Insider program, and so I can't really figure out how I got on an Insider build for the NGSC. On my older machine I originally installed the client when I think it was still in beta and the Groove client was still the officially supported OneDrive client, so maybe that put me on an insider build from the beginning? But my Win 10 machine I just got in October, and I thought I just installed the client the normal way after following a link from Office 365? Or did it come preinstalled with Win 10? I can't remember anymore, and I haven't been able to find a way to get to the production client. Can I just uninstall and reinstall?
As for templates, that is something that we had tried in the past and had trouble with. We work with a revolving set of external consultants, and we found that templates were not well understood and files tended to get screwed up. Plus, we never know which files we will want to be a template in the future. Typically when I put together a client proposal, I try to go through the last two decades of projects we've done and find the one that is the closest and start with that, and then bring in pieces from other proposals until we get something that fits for the current project. But there's not really any standard starting place.
I like the idea of turning autosave off, but from your link it appears that the only way to do that is on a file by file basis, which misses the point for me, if I can remember to turn off autosave then I could remember to save a copy...but I'm looking to insure for the times that I forget to do that. I want to make sure I both lose the original file or the modified date, and it seems like the only way I can reliably do that is to store our files somewhere besides Microsoft's servers?
Office updated today to the production version, and after it did that I was once again able to take the file that had autosaved and restore to the previous version, which is an improvement. However, the modified date changes to the current date when I do that instead of the original date. It seems I will have problems opening files without changing the modified date unless I immediately turn off autosave every time I open a file?
I still haven't been able to figure out how to move to the production update ring for OneDrive. I uninstalled the client and then downloaded the installer from https://support.office.com/en-us/article/Deploy-the-new-OneDrive-sync-client-in-an-enterprise-environment-3f3a511c-30c6-404a-98bf-76f95c519668#cad and it just installed the same version again. Is there a different source I should be using to download the installer?
I'm still having issues with not being able to send a link to a OneDrive/SharePoint file. Have not had enough time to experiment and see if other syncing problems have been resolved.
