SQL Server Reporting Services (SSRS), when integrated into SharePoint 2013 enables reports to be sent to users via email. From the report click Manage Subscriptions.
On the following screen click Add Subscription. You can configure the report options and click OK to save.
If you’ve not configured SSRS you may receive an error in the Application Event log on the SharePoint server hosting the SSRS service application. This could take the form:
The Report Server Email extension failed to read its configuration settings from the rsreportserver.config configuration file. The extension is not available to users. (Application: SQL Server Reporting Services Service Application, CorrelationId: …)
The web page may also fail to load, with an error like the one below.
If you encounter this error, open the SQL Server Reporting Services Service Application from Central Administration. Next, open e-mail settings and configure the SMTP server. Finally, open Provision subscriptions and alerts, enter the appropriate account details and click Ok.
Following an upgrade to SharePoint 2013 and claims based authentication, SSRS reports fail to load and you receive the error “Microsoft.SharePoint.SPException: User cannot be found”.
Unfortunately, many blog posts and forum entries say that you have to reload all the reports and data sources and I’ve been unable to find any alternative. What I describe here is my attempt to make the process of reloading reports and data sources as painless as possible.
Within SharePoint 2013, navigate to the SSRS report library. Take a note of the configuration of each data source as you will need it later. Next, take a note of the data source used by each report. Next, from the ribbon, choose to “Open with Explorer”.
Within the Explorer view highlight all the report and data source folders. Copy and paste the contents to another location, e.g. local hard drive, or network drive.
Now select all the folders on the local drive and copy and paste them back to SharePoint 2013, overwriting the existing files. I found that following this process the data sources became disabled, so for each data source edit the data source definition, re-enter any credentials and enable the data source.
Once the data sources have been configured, reconnect each report to the appropriate data source.
If anyone knows of a better way, which doesn’t involve redeploying all the reports and data sources, please let me know!
Following an update of a SQL 2005 SSRS server to SP4 + all Windows Updates, the SSRS service would not start. “Report Server (MSSQLSERVER) cannot connect to the report server database.” was logged in the Application Event Log. “Timeout (30000 milliseconds) waiting for the SQL Server Reporting Services (MSSQLSERVER) service to connect.” was logged in the System Event Log.
The resolution was to update the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout registry key to 60000. This increases the time allowed for a service to start from 30 seconds, to 60 seconds. In my case the registry key didn’t exist so I had to create it. Once the registry has been updated/created reboot the server.