Introduction:
There are a couple logical steps to take to troubleshoot any error or issue that arises while users attempt to access the SSRS reports from a report library in SharePoint integrated mode. If a user complains that a report does not properly render or that an error is given after clicking on a report there are a couple logical steps to take in order to quickly identify the issue and resolve it. Some steps that I typically take are listed and described in the following section. I think you will find that Steps 1-4 apply more to an existing and previously functioning SSRS installation, while Steps 5-9 will apply more to an initial installation and configuration of SSRS in integrated mode.
Solution:
1. A good first step is always to have the user totally close out of their browser and navigate back to the reports library. Sometimes cached internet settings can prevent reports from updating properly.
2. If this does not fix the issue for the user, try to reproduce the issue with an Administrator account. If the Administrator cannot reproduce the issue then specifically check the individuals credentials and ensure they have the proper access to view the report.
3. If the Administrator can reproduce the issue, attempt to run another report in the same report library and if possible another report that exists in a separate report library. Depending on the results the issue could be identified within this step as an issue with the specific report library rather than the entire SSRS installation.
4. Another place to check for an error would be the actual SSRS reports. SSRS reports are developed in a tool call Business Intelligence Development Studio, commonly referred to as BIDS. Navigate to the server where the reports were developed and open BIDS. Open the report that the user is having issues with and click on the "Preview" tab. This is done to verify that there is not actually an issue with the report itself. If the report has no issues, then the output window will show that there are no errors or warnings. This message is highlighted below in red showing that in this example the report definition has no issues. If applicable, select the necessary dropdowns and click "View Report" to execute the report. This will ensure that the report can successfully retrieve data from the shared data source. If the report successfully displays then it is unlikely that there is an issue with the report data sources.
5. If the error can be reproduced by another user and runs fine in BIDS, navigate to the server that contains the installation of SSRS. This server is a good starting point when trying to trouble shoot what is wrong with an entire installation of SSRS. Navigate to the Start Menu and open the "Reporting Services Configuration Manager". When the configuration tool opens, check to ensure that the status of each one of the menu items are properly configured and not showing any errors. When the configuration manager is setup properly it means that the Windows Service Identity and Web Service Identity domain accounts are properly configured. Furthermore, this proves that the Reporting Services databases and SharePoint Integration are still configured properly. In this step you can also ensure that the domain accounts you use have the proper access to both the SSRS installed databases and SharePoint databases.
6. Check the SSRS Integration settings in Central Administration. If these are not properly configured then this could potentially be causing the issue.
7. If everything passes within the configuration manager and central admin, open an Internet Explorer browser and navigate to the report server, in my case http://[servername]:81/ReportServer. If Reporting Services is able to access the SharePoint content databases as required a directory of SharePoint sites should be listed as shown below:
8. If the web browser properly displays, it would be worthwhile to see if the SSRS application pool is running in Internet Information Services (IIS) Manager. This step is relevant for SSRS 2005.
9. If everything in IIS looks correct, then the specific error may be need to be further analyzed. I recommend the MSDN and TechNet articles. I have found that sometimes SSRS will fail because SQL Server or SharePoint are not up to date with the available patches and/or hot fixes. You will find that this step will apply more often on the initial installation of SSRS rather than an existing configuration that is giving an individual user an error (although I always strongly recommend keeping up on patches!).
