I recently worked with our SharePoint administrator to install SQL Server 2012 Reporting Services in SharePoint Integrated Mode to take advantage of PowerView. By following the installation instructions found at this MSDN article, we were able to painlessly install both Reporting Services and the Reporting Services Add-in from the SQL Server installation media.
Then began the configuration process. Since everyone’s environment is different, I found it difficult to troubleshoot some of the odd behavior that we were running in to. In Part 1 of this post I want to focus on what we did to overcome a specific error we were receiving:
After installation, I created a Business Intelligence Center site without any trouble. In the Connections library, I would attempt to add a Report Data Source and receive a SharePoint page that detailed the following error:
This SQL Server Reporting Services (SSRS) functionality is not supported. Use Central Administration to verify and fix one or more of the following issues:
- A report server URL is not configured. Use the SSRS Integration page to set it.
- The SSRS service application proxy is not configured. Use the SSRS service application pages to configure the proxy.
- The SSRS service application is not mapped to this web application. Use the SSRS service application pages to associate the SSRS service application proxy to the web application.
Other times, I would receive a little bit more of a generic message saying something to the effect of “This SQL Server Reporting Services (SSRS) functionality is not supported” or “Unsupported Reporting Services Functionality”.
As it turns out, our specific problem was unrelated to any three of those bullet points.
On the Feature Selection screen of SQL Server setup, you can simply choose “Reporting Services Add-in for SharePoint Products” on your other WFE nodes. You don’t need to install the Database Engine Services or Reporting Services – SharePoint all over again…just the Add-in.
We began to suspect it was something related to missing components on the other nodes because as I was troubleshooting, I noticed that if I attempted to create a Report Data Source enough times, I would be able to proceed to different stages of the creation process. Sometimes I would hit the error right away. Sometimes I would get to the page where I could fill out the connection details but when I would attempt to save the data source I would get one of the error pages described above.
After we installed the Reporting Services Add-in on all WFE nodes, the problem stopped and we have not experienced any difficulty since.