I'm running Windows 10 and I have Office 365. It's my personal PC, not using Active Directory.
When I'm trying to use OneDrive and when I open it, I get this error:
We cannot synchronize your documents anymore
I tried sfc /scannow, ccleaner and others tricks. No change at all.
I'm thinking it's due to Office 365 connected to my OneDrive PRO.
Anyone have any information about this issue?
I read the microsoft forum and many people face the same issue.One of the solution I came across is:
Hey everyone. I just found what might be the solution in another discussion thread on this same forum. It is suggested to Uninstall the new OneDrive for Business. You should see it in your Programs and Features control panel.
Here is the link for further info
https://answers.microsoft.com/en-us/onedrive/forum/odfeatures/microsoft-onedrive-notification-on-desktop-we-cant/0e20fca5-832c-4928-9438-71484fba3255
Related
First all first, I am free Power BI desktop user, so I am not Signed in and don't have an account in Power BI.
Since last Update I encountered an issue, and that is spamming with Sign in window anytime I am trying to use some templates that I downloaded from internet. I NEVER had this issue before, I could open all the templates (pbix files) without any trouble, but not since I open I am constantly getting Sign in window and can't get rid of it actually. So, I must terminate app to close it.
I tried to reinstall, to fix it, but problem is still there. Do anyone got an idea what could be a problem? Is Microsoft "blocked" usage of custom visuals for free users or something?
After UPDATE for June 2020, problem solved automatically!
Thanks to Microsoft =)
I've just uploaded several hundreds of files to my Sharepoint Online libraries. I was wondering what would be the best solution to have them syncronized or kind of a network drive in my WS2008.
Microsoft recommends using the OneDrive Sync client, so here is the Link to the install instructions from MS as a standalone package. Choose the 32-bit version even if your OS is 64-bit. In my experience with Office rollouts it is still (!) the version giving the least amount of headaches.
Using the OD4B client the files you choose will synchronize to the server. Please note that it is a two-way-sync and if you delete something on the server this will be done in SharePoint as well.
Map to network drive (i.e. via WebDAV) is still possible in SharePoint Online, but it is not reliable and disconnects often due to authentication requirements.
I'm using SharePoint 2013 and some users, I'll repeat, only SOME of them can't open office files in their client application (word, excel...). I don't know what is the problem because I can open documents from my machine but when I log in to another machine (colleague that can't open documents) I'm also unable to open documents. So, problem is in machine. I tried:
removing office cache files
Adding SharePoint site to Trusted zone
Repairing office installation...
Nothing helps. Message after a longer period of "downloading": Sorry, we couldn't find . It is possible it was moved, renamed or deleted?
Sometimes there is an another message...
UPDATE:
Problem is solved by installing newest updates (from 5. December 2015. to 15. December 2015.). I'm not sure but probably this update solved problem:
https://support.microsoft.com/en-us/kb/3023068
Thanks everyone for support
Look at your installed Windows updates. If you have KB3055034, uninstall it and see if that helps - worked for us!
The solution we found that worked like a charm was deleting the counters.dat file out of the user's Temporary Internet Files. Please see the steps below:
Close all instances of IE and other browsers
Delete counters.dat file (location: \AppData\Local\Microsoft\Windows\Temporary Internet Files\ )
Reopen IE or other browser
This worked like a charm and has been a big help with other tough fixes like plugin issues.
I have a VBA project that uploads data from an Excel spreadsheet to an Access database stored on SharePoint. All was well until I upgraded to Windows 7. Windows 7 doesn't automatically pass Windows authentication to SharePoint when accessed this way. Now my project will not update my db. How can I get my VBA project to pass that information to SharePoint? I've been searching for 2 days and I haven't found anything helpful.
I ran into the same problem today. The workaround I came up with, which I would love to replace, is to force Windows Explorer to open the sharepoint folder, which triggers the authentication request to the user. Obviously, there are many issues with this solution.
I had two clients with a save issue in SharePoint.
When they try to save they would get a a very generic error: "Document Could not be saved"
The only way they could get them into SharePoint was by:
Saving to local File System
Using the Upload option from the SharePoint menu
Configurations
Client 1: Vista and Office 2007
Client 2: XP and Office 2003
I was able to fix client 1 by having him Map a Network Drive to the Sharepoint Site.
After mapping the network drive, somehow the OS magically knew about the SharePoint documents folder and he was able to save.
I'm not having the same luck with Client 2.
It won't even let me map the network drive. I get an error (one that I did not take a screenshot of and don't remember the exact wording...sorry). but it was an error trying to map the network drive to the SharePoint site.
So, after some Googling, I had him go to Windows Update and download all the latest patches for his OS.
He claims he did, but is still getting the problem.
Before I do another WebEx and start taking stabs in the dark to try and fix him, I was wondering if any veteran SharePoint users have run into this same issue and what they did to fix.
Or, is there some OS setting I should be looking at that needs to be toggled/modified.
I can access his SharePoint site just fine from several PCs and make modifications and save as necessary.
Did you try running the Microsoft Office Diagnostics?
Start --> Microsoft Office --> Microsoft Office Tools --> Microsoft Office Diagnostics
Let that scan and repair any issues it finds and see if that helps. That tool has fixed similar issues for me many times.