- Microsoft onedrive for business 2013 how to#
- Microsoft onedrive for business 2013 install#
- Microsoft onedrive for business 2013 update#
- Microsoft onedrive for business 2013 windows 10#
Given my preference for avoiding regular (repetitive) root canals, I am concluding that I need another solution. When that doesn't go so well, theyĪdvise completely uninstalling Office (not just ODFB), then resyncing. Takes days, as I have lots & lots of files stored there. Four times over recent history MS has advised me to break the sync, uninstall ODFB, then reinstall & resync. Of local files not synced with the cloud copy.
Everything works fine for a couple months, then sync errors begin to pile up.
Microsoft onedrive for business 2013 install#
After install of Office & ODFB, I choose to sync a lot of files stored on ODFB & Sites. I don't think any of that makes much difference, as the issue is reportedĪcross lots of hardware platforms & Windows versions.
Microsoft onedrive for business 2013 windows 10#
I am running Office 365 (E3) subscription on a Windows 10 Dell XPS15. I have been struggling with ODFB for quite some time. Maybe a dead thread at this point, but not a dead issue. I am running Office 365 Small Business Premium with all the latest updates. You to escalate this because as BayTree noted - people are starting to give up on ODFB and go with other options. ODFB failing to sync and ballooning OfficeFileCache. This issue has been happening to a lot of people. I have searched several threads in the past week to try to solve this issue. I use task manager or Resource Monitor to kill Groove.exe and/or when they start back up - they do it again. The folder \Users\xxx\AppData\Local\Microsoft\Office\16.0\OfficeFileCacheĬurrently has 26 GB of size.
The C Drive has filled up though with over 20 GB of data when the ODFB is trying to sync. Thing is - my ODFB folder is set to sync to a 2nd Hard Drive (X Drive) not where my User folder is (C Drive). These two programs are sucking up my processor - maxing out at 100% even after ODFB says it has synced up all files. So far I have not found a fix to this issue. Yes - unexpected issues is an understatement.and the critical issue. Neither had sync issues.Īs Melon noted "sometimes the conflict between MSOSYNC.EXE and Groove.exe may cause some unexpected issues". I have 3 computers - 2 did not have Office Pro installed, but were/are both running Office 365 2013. Try listening to that for 30 minutes straight. I even had one time where the computer kept making theįile open clicking sound ever 5 seconds until i uninstalled ODFB. I did the ODFB repair and troubleshooting recommended by Microsoft and you here too. My issues were similar to BayTree - continuous syncing with ODFB without files actually showing synced. I have run Office 365 Repair (simple and advanced). Uninstall Office Pro to clean up 2 office programs.
Microsoft onedrive for business 2013 update#
Then I tried install Office 365 2016 click to Run thinking an update
Microsoft onedrive for business 2013 how to#
I uninstalled/reinstalled (u/R) ODFB, OneDrive Personal, ran Repair on Office Pro, ran Repair on Office Upload Center (when prompted - cannot figure out how to run without prompt). I know at least 1 other person I work with that had similar challenges and just gave up and bought DropBox space. Up recently since my understanding is ODFB is hosted there. Or mabye it was something related to the SharePoint service that have been acting Not make any registry changes or added programs that would have impacted this.so my best guess is it came through a Windows Update.maybe when they launched Office 2016. About 2-3 weeks ago I started getting this problem with OneDrive for Business bogging down my computer. Melon - I had Office Professional 2010 and Office 2013 365 installed - similar to BayTree. I have - posting for others that may be looking for a quick fix:Ĭ:\Program Files (x86)\Microsoft Office\root\Office16\groove.exe I might use based on what OneDrive for Business did to my computer and weekend! Seriously though - thanks! My folder location was a bit different based on the Office program BayTree - thank you - this is a nice short term fix.
0 kommentar(er)
