Forum Discussion
Users experiencing Upload Failed errors after editing files from Sharepoint
Hi,
Regarding this issue we found “in our case” that upgrading Office release to (1705) from in many cases 1609-1611 and probably even older in some cases somewhat decreased this happenings.
However the problem still remained for many and @ this time we encountered another issue in our environment an actual error, our “group policy” did not apply as it should, the start page got the right zone “Local intranet” but as soon as users moved on to another site in the farm these sites where executed in “unknown zone”.
After some tests and listened to rumors we found that or domain just where to short so adding the whole url in our gpo did the trick, we always used like *.domain.com and this never been an issue before but this farm only has two chars in the domain name so our gpo where like *.xx.com and rumors told us that it should be more chars for stability so we entered more chars in our case the whole url: intranet.xx.com & problem gone.
Hope this can help at least someone out there.
/Robert
We bypassed riverbed for all sharepoint traffic and it seems to have fixed it.
We have a similar problem, but it is intermittent. Occasionally a user cannot save a document back to SharePoint after editing it in Office. SharePoint (or Windows?) forces the user to save an Excel, Word, or PowerPoint document under a different name, or in a different location.
We end up with multiple copies in SharePoint with different names, or else the user saves it offline and sends it to me to enter their changes in the SharePoint version. Does anyone else have this problem, or can you suggest a fix? I am recommending users edit in the browser as much as possible, but occasionally they need the full power of the Office application.
We have also noted that when editing a SharePoint Excel document in Excel, the "Save" icon does not have the Shared indicator--the circular arrow on the icon. Usually it saves just fine, but occasionally we get the error and cannot just "Save" but must "Save As."
We don't use Riverbed. We are on SharePoint online using Office 2016 or Office 2010.
