I needed to create the excel Services, initially an easy and fast task to execute throught CA. But not so easy ended.
PROCEDURE
- Creating the service:
- Starting the service on the app server you choose
- Associating the web application with the service: That´s the point that in fact fails behind the scenes, on the SQL part.
ERRORS ..
In fact I got different errors in 2 farms. The ULS logs show:
Farm A: there was an error in communicating with excel Calculation
Services http://
…. Exception: the remote server returned an error: (403) Forbidded
FARM B:There was an error in communicating with Excel Calculation Services http://AppServer:32843/ceaafed8560b789456b1c0b95625c889a/ExcelService*.asmx exception: The remote server returned an error: (403) Forbidden. [Session: User: DOMAIN\poolaccount].
In the application Log you might find:Unexpected error when trying to access service settings in the configuration database. Make sure the proxy for this service application is a member of the default proxy group for the active web application. Error = ExcelServerWebServiceApplication.Local: Could not get the web application associated with this context. This indicates that the Excel Server service is not properly registered or provisioned..
SOLUTION
After some research I found out that Microsoft already published the
issue/workaround. It seems that when you create the service after the
installation of the farm the privilege that the service account needs to
access to the content database of the web application is missing. You need to
do it by command line. The nice thing is that it´s working properly:
- $w = Get-SPWebApplication -Identity http://portal
- $w.GrantAccessToProcessIdentity("domain\serviceaccount")
- $excel = Get-SPExcelServiceApplication
- $excel.Provision()
Thanks!!!!!!
ResponderEliminar