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.
Related
My company uses a SharePoint site for our department where we share resources and documentation. We currently have a primary Excel sheet linked that contains a massive amount of our day to day info and our most common hurdles and pertains to about 80% of our workflow. This was created before the company switched (recently) to Office365 and the web based applications vs the standalone programs. Now it is not letting anyone open the the sheet because it is still trying to open in the Excel program and not the web app.
We previously used Office '13 and there was never any issue. The link is meant to open the Excel sheet right up in a read only capacity and not save the program because the content is being updated regularly with new information and regulations. With the "upgrade" from the older version of Office to the 365 web based standard version this link no longer opens the file directly, it saves to the PC and then needs to be loaded to the web app from the saved version which completely negates the ability for it to be dynamically updated. Inversely, we could import that into One Drive and update it to the new system and set the link to the view only shareable link but that would take an excessive amount of time to reformat and edit on top of everything else. If that is how we need to do it then that is how we need to do it, but is there anyway to just update the link already in the system so that it can allow the file to be opened in the web app as well as the stand alone for those not upgraded yet or with the advanced version (managers) that still uses the programs and not the web apps?
I expect the file to be able to be opened in Office365 Excel web app read only as opposed to being saved to the local machine and if possible also be opened directly in the standalone Excel program for those using the 365 Advanced version or who have not yet completed the upgrade process that the company is currently rolling out.
Thank you for your time with this.
We solved this by simply upgrading the whole department and to the Office 365 Advanced version circumventing the entire issue, thank you for your time regardless.
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 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
I just bought an Office 365 family account, and installed Excel on my Windows.
However, I cannot find "manayge my add-ins" where we could upload an xml for testing. I have been always using excel online to test my xml/addin.
Does anyone know what's wrong here?
Side-loading on Windows is a bit different. You need to setup a network share and store your manifest file there. Once you configure your client, it will automatically start picking up manifest files from that directory.
See Sideload Office Add-ins for more complete details on this process.
can someone please tell me what i need so that i can see the explorer view for a library in sharepoint? it works on one machine and not another. it sometimes works on a vista client but not xp. it works in internet explorer but does not work on another machine with the same settings.
please help. wss 3.0 on windows server 2008 with vista and xp clients.
Thanks
It requires WebDav to be enabled on the server part, and WebClient to be running at the client. WebClient is just a service, see this technet entry for specific information on how to start it.
If WebClient is already running, make sure the SharePoint site is added to the "Trusted Sites" in IE. In Vista SP1 and up, the WebClient has a private list of "Trusted Sites" in the registry.
SharePoint explorer view actually doesn't work in IE8 on Windows XP SP3. The issue only occurs if your using SSL, and I've not seen a good solution to make this work. Interestingly, it works fine in IE7. Now if your using any other web browser besides IE, there is no way to get explorer view to work currently.
Also, the 64bit version of IE is a Level 2 browser with SharePoint 2007, so certain features don't work on that either. I think the explorer view is one of them, but my memory could be wrong. Microsoft has published what currently does and does not work between different browsers on SharePoint.
Make sure you have a site collection located at your web application root. This solved the problem in my case.
Problem : explorer view not working properly, except when :
explorer view selected in a subfolder of the document library
a network favorite pointing to the document library was created
I was trying to do a quick backup of a bunch of files, and the explorer view was not working. What finally worked was mapping a network drive to the sharepoint server, and then I was able to bulk copy and paste the folders/files to my backup server.
I don't know why MS makes so many things really difficult. But they do. But that worked for me.