Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, April 11, 2017 9:01 PM
In my SharePoint Server 2013 Enterprise on premise environment that is fully updated to 15.0.0.4911, when you use Chrome and click on the Name of column of an Excel file it downloads a copy. If you use the ellipses menu and click EDIT, it opens from server.
I know there were issues previously because of NPAPI support removal. The August 2016 CU was supposed to fix, which we have.
The library is set to Open in Client Application.
We don't set any Chrome policies.
Word documents open fine.
We don't use Office Web Apps.
Chrome is Version 57.0.2987.133.
We are currently using the ellipses menu EDIT button as a work around but it is difficult to guide many users to this when they are used to just clicking file name.
I have searched online and don't find recent reports of this issue. I would greatly appreciate any ideas on what to check. I have this duplicated on a dev server so can try most things. Thanks in advance!
All replies (7)
Wednesday, April 12, 2017 9:50 AM ✅Answered
Hi Josh,
I tested the same scenario per your post in my environment and I got the same issue as you got.
However, I also found that if I use Edit button to open a document first and then click the document name to open the documents, all the documents would open in client application instead download before I closed the browser. But if I only click the document name to open the document, the document would be downloaded only.
You can use Edit button for the first time as a workaround when you are using Chrome.
Best Regards,
Victoria
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Wednesday, April 12, 2017 3:30 PM ✅Answered | 1 vote
Yeah, pretty sure that argument has been beaten to death by all SP admins. The fact is that SP is MS and so is IE, plain and simple. They're only fully compatible with each other and nothing else.
cameron rautmann
Wednesday, April 12, 2017 2:16 PM
Hi Josh- this plugin/update may help with your issue:
cameron rautmann
Wednesday, April 12, 2017 2:38 PM
Victoria,
Thanks for the reply, we are already guiding users to use that as a work-around. With 5,000 users worldwide, we get a-lot of support calls for this. I am looking for a permanent solution that doesn't require users changing their behavior.
I do appreciate your reply, and any other information. I am hoping someone has found a solution.
Wednesday, April 12, 2017 2:42 PM
Cameron,
Thank you for the link. I am familiar with the post. I was the second person to comment on the article in 2015. Our environments have the August 2016 CU and more recent updates.
Let me know if I am missing something or you have any other ideas. Thanks again!
Wednesday, April 12, 2017 2:49 PM
Send out an email blast to everyone and tell them to only use IE ;)
You're going to have issues with Chrome beyond this. The simplest answer is for everyone to just use IE.
cameron rautmann
Wednesday, April 12, 2017 3:11 PM
We have tried many communication channels for all employees. We always recommend our users use IE, especially for any document management related tasks. This keeps coming up though and management is demanding a solution. Maybe I will have to open a case with MS, but not sure that will even result in a solution since they can't change how Chrome interprets their UI.
Thanks again for the input. I am glad I am not the only one making that recommendation.