Excel Services Fix - "The workbook cannot be opened"

The workbook cannot be opened

​This is a general issue with many SharePoint users while opening an Excel workbook (.xlsx) in the browser the error "The workbook cannot be opened" or “The site is not added in trusted location”.




But if the file is opened with Workbook in the desktop client it will not have any  problems with it. The root cause of this error message is due to below reasons:

 a)      The URL user is trying to access is not correct/wrong.

 b)      The document library settings for opening the files in browser mode.

 So in order to overcome these simple error message we need to make sure that we are using the correct URL and other library settings are in place as per recommendation.

a)      On the <document library>: All Documents page, under Library Tools, click Library

b)     In the library toolbar, click Library Settings.

c)      On the Document Library Settings page, click Advanced Settings.

d)     On the Advanced Settings page, in Opening Document in the Browser, select one of the following options:

-        Open in the client application   When a user clicks on a document in this library, the document will open in the corresponding client application (if available).

-        Open in the browser   When a user clicks on a document in this library, the document will open in the Web browser Web app for that document type. When the document is opened in the Web app, the user can then decide to open the document in the client application

-        Use the server default   When a user clicks on a document in this library, the document will open by using the default open behavior specified for the server on which SharePoint d)     On the Advanced Settings page, in Opening Document in the Browser, select one of the following options:

Comments

Post a Comment

Popular posts from this blog

Creation of Secure Store Service Application failed because of the following errors: The Timer Job Completed but failed on one or more machines in the farm.

Image
Unable to start Secure Store Service : Error : Creation of Secure Store Service Application failed because of the following errors: The Timer Job Completed but failed on one or more machines in the farm. Solution : Delete the Secure Store Service Application. Close all the browsers and runt the sharePoint Configuration wizard and retry to configure the secure store service and the issue should be fixed. If the issue still persists , start the Secure Store Service Application using the following commands. $proxy = Get-SPServiceApplicationProxy | where {$_.TypeName -eq "Secure Store Service Application Proxy"} $proxy.Status = "Online" $proxy.Update() In few cases it may happen that the Proxy service may start and the secure store service still has an error.In this case please delete the Secure Store service  and recreate using PowerShell as below : $sa = New-SPSecureStoreServiceApplication -Name "Secure Store Service Applicatio...
Read more

SharePoint Latest Interview Questions- July 2016

SharePoint Latest Interview Questions July 2016: 1  Internal pages are not appearing in search results? How do you troubleshoot? 2  User is getting the error “Server is unavailable error.” How to troubleshoot? 3  How to create multiple web applications on Port 80 4  STSADM and PowerShell command to backup Site Collection. 5  Steps to Promote Sub Site as Site Collection. 6  How to restore a Sub Site in SharePoint? 7  Is it Possible to restore SharePoint backup file on SQL? 8  What is new in user profile service in SharePoint 2013? 9  Unable to search Document in Search? How do you troubleshoot? 10 Search scope, People scope is missing, what do you do? 11 Difference between IIS 6 and IIS7? 12 Create External accessible website(AAM)? 13 Steps to Create Binding in IIS.? 14 What is the SPO management shell command to connect as admin 15 Explain SharePoint evolu...
Read more

Migrate Secure Store Service Application from SharePoint 2013 to SharePoint 2016

Image
Migrate Secure Store Service Application Whenever we migrate SharePoint from one version to the next version , we recreate most of the service applications. However, in few cases where we have dependencies  with service applications like secure store and Managed metadata service which may have several credentials and term stores. recreating all the service IDs may be a tedious job and can easily land us in to issues. Hence, it is recommended to upgrade the Secure store service application.  Title: Steps to Migrate Secure Store Service Application from SharePoint 2013 to 2016 In on of my SharePoint Migration Projects from SharePoint 2013 to SharePoint 2016  Secure Store Service Application was one of the critical services used by the customer due to its dependency with Data Refresh Jobs from SSAS.  This article is a step by step approach to migrate Secure Store from SP 2013 to SP2016. Steps: Identify the Secure store database used in the SharePoint 2013 Database and r...
Read more