Thursday, July 17, 2014

How to resolve "The requested service, 'http://:port#//ReportingWebService.svc' could not be activated" error when creating Power View report



After we installed and configured PowerView for SharePoint 2013, we have constantly run into stability issue when creating Power View report. The symptom is users will randomly get the following error message when click “Create Power View Report” as indicated in the screenshot.


I’ve tried the following two different ways people mentioned but not be able to resolve the issues.

  1. Check Rssrvpolicy.config file mentioned by Mike Yin
  2. Change the Enable 32-Bit Applications property of the IIS application pool for the SharePoint web application to False published in PrologikaForums (Note this will stop app pool and make it unstable!)

If you check the ULS log, it will show the following error:
“System.ServiceModel.ServiceActivationException: The requested service, 'http://spsbx15:32843/586f5b2b0ac34da6b57e9dd817fa06d3/ReportingWebService.svc' could not be activated. See the server's diagnostic trace logs for more information.”



This seems to point to the reporting web service issue from this log. After review the SQL Server Reporting Services 2012 SharePoint integrated mode Endpoints architecture, I found the solution is to restart the app pool that is running report service. Here isthe details procedure to found the app pool that is running report service.

1. First run the PowerShell command to identify reporting service reporting service process ID.

PS C:\> Get-SPRSServiceApplication



Name                   Id                                   UEAccountName
----                   --                                   -------------
Reporting Web Service 586f5b2b-0ac3-4da6-b57e-9dd817fa06d3  


You could verify the report web service status using the ID but remove all the "-" inside
to construct the following URL. You will see nothing will be displayed. The port # can be found in steps below.




  2.  Browse IIS manager "SharePoint Web Services" with this ID and click "Advanced Settings..." to
identify application pool ID that runs reporting service. In this case, the ID is "a106ffe3b2e74f5b9b77bd1f4312129f". You can idntify the port # for the service. In this case, the port # is "32843".



3. Browse IIS manager "Application Pool", select the pool with the ID ("a106ffe3b2e74f5b9b77bd1f4312129f")  from step #2. 

You could verify this is the application pool runs report service by right click "View Applications". You should see the applications it runs.

4. Restart the application pool and view the report service URL. You will see response displayed.



Now you have not only the way to fix "ReportingWebService.svc could not be activated" issue, but also have a way to verify the report service availability though report service URL. We might need to configure a monitor to constantly check this web servcie and automatically restart the application pool whence it was not reponse. 

We are continue working with Microsoft to resolve the stability of the report service stability issue.


2 comments:

  1. This is a good article & good site.Thank you for sharing this article. It is help us following categorize:
    healthcare, e commerce, programming, multi platform,inventory management, cloud-based solutions, it consulting, retail, manufacturing, CRM, technology means, digital supply chain management, Delivering high-quality service for your business applications,
    Solutions for all Industries,
    Getting your applications talking is the key to better business processes,
    Rapid web services solutions for real business problems,
    Web-based Corporate Document Management System,
    Outsourcing Solution,
    Financial and Operations Business Intelligence Solution,

    Our address:
    2002 Timberloch Place, Suite 200
    The Woodlands, TX 77380
    281-364-1799

    prologic-corp

    ReplyDelete
  2. I have this same error for my SharePoint 2010. I followed your solution and it does not work for me. I am getting "The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that \$ has Read access to the physical path. Then test these settings again." when I click on the "Authorization" results. Authentication is good.

    I am using a domain (SQLBIGEEK\Administrator.local). If you can show me a step by step process to get this "Read" access, I would greatly appreciate it. I have seen solutions on line talking about how to fix this issue but they don't show how to do it step-by-step. I am a novice with Active Directory and IIS so I don't understand what I have to do. Thanks.

    ReplyDelete