SharePoint 2010 offers a wide variety of features that make our work lives easier, but every now and again, SharePoint can still be less than kind to users.
Challenge:
When I was trying to open an Excel 2007 spreadsheet once, this error came up unexpectedly:
And then:
Which was followed :
Hmm. So I started investigating to determine the source of the problem, gathered all of the solutions I found to be potentially relevant, and was finally able to get my Excel Service up and running. If you are experiencing any of the above errors, hopefully the information below will help you to find the solution to your own problem.
Solution:
Possible Causes:
- The SharePoint 2010 Excel Services Application has not started properly.
- The Security Token Service Application is not started properly.
- The Excel Service account does not have permissions for the SharePoint content database.
Resolutions Checklist:
Step 1: Go to Central Administration -> Application Management -> Manage service applications -> Verify that the Excel Services Application and Security Token Service Application have started.
Step 2: Go to Central Administration -> System Settings -> Manage services on server -> Verify that Excel Calculation Services has started.
Step 3: Go to Central Administration -> Security -> Configure service accounts -> select Service Application Pool – SharePoint Web Services Default if you are using out-of-the-box SharePoint Excel Service; if you have created a new application pool for your Excel Service, select it instead. Note the service account currently being used.
Step 4: Verify that your service account includes the db_owner role in the SharePoint content database of that Web application. You can do this in SQL Management Studio on your SQL Server, or using the following PowerShell commands to grant permission to your service account:
- On the SharePoint Server, click Start -> All Programs -> Microsoft SharePoint 2010 Products -> SharePoint 2010 Management Shell.
- Enter these commands:
1: $w = Get-SPWebApplication -Identity http://portal
2: $w.GrantAccessToProcessIdentity("domainserviceaccount")
Step 5: Provision the Excel Services Application running these PowerShell commands:
1: $excel = Get-SPExcelServiceApplication
2: $excel.Provision()
Step 6: Open IIS Manager on the SharePoint Server, and verify that SecurityTokenServiceApplicationPool has started.
Step 7: Reset IIS
Notes:
- This blog post only applies to SharePoint Server 2010 Enterprise.
-
This blog post was written with basically the out-of-the-box SharePoint Excel Services Application in mind, and may not cover problems arising from customizing Excel Service.
See also:
- Excel Services 2010 Error – “The workbook cannot be opened.” [stack exchange]
Hi nice article.
I faced one of those problems on my Sharepoint Foudation 2010. If could advise something, I would really appreciate it.
Here is description of my problem:
“We have Sharepoint Foundation 2010 installed standalone, and Office web apps installed as well.
Everything was working fine till this day when it started to give error when trying to open Excel file in browser.
When I click on file I’m getting authentication window which won’t accept my credentials for three times, and then it gives me this error: “An error occurred when trying to perform requested action. Please try again.”.
I have no issues opening Word documents, but Excel just won’t open now.”
Hi Taras,
Maybe this will help:
social.technet.microsoft.com/…/b5988534-d430-4e58-b4d7-2266ecd4655c
If not, please contact Microsoft to resolve the problem. Unfortunately, I couldn’t advise anything further because this will need to be troubleshooted in deep to reveal the root cause..
Hi Duy Do,
Could you please advise, how can I proceed with disconnecting server from a farm if this is a standalone server?
Apperciate, your help.
Hi Taras,
Sorry I missed the fact that you are running on a standalone SharePoint. I found that article and thought it could help, but apparently it does not. You cannot remove the standalone server. Please contact Microsoft to troubleshoot this issue.
Regards,
Hi Duy Do,
I got it fixed simply restarting Microsoft SharePoint Foundation Web Application service In Central Administration > Application Management > Services on Server.
Thanks for your help!