Troubleshooting Report Processing and Rendering
Use this topic to troubleshoot issues that you encounter when you run reports.
For more information about ways that you can troubleshoot a report, see Troubleshooting Techniques for Report Issues.
For issues about report performance, see Troubleshooting Report Performance.
rsProcessingAborted and rsErrorExecutingCommand Errors
The following error combination occurs when the data source connection is missing or invalid.
"An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for data set '<datatset name>'. (rsErrorExecutingCommand)
Invalid object name '<object name>'."
Verify that the connection string is valid for the data source.
For more information, see Reporting Services Errors and Events.
An Unexpected Error Occurred During Report Processing on the Server
If you are logged on to the report server by using local administrator credentials, you can view the call stack if you right-click the page and select View Source. More information is provided in the call stack.
An Unexpected Error Occurred During Local Report Processing
You might see the following error message when issues occur with the local data cache (.rdl.data) file: "An error occurred during local report processing. Index was outside the bounds of an array."
Determine to which dataset the out-of-bounds index refers. Close SQL Server Business Intelligence Development Studio and delete the appropriate .rdl.data file for the dataset. Open BI Development Studio and run the report again. This recreates the cached data with the appropriate index bounds.
Toggle items do not work
If a report generates without errors, but toggle items do not work (for example, you click an expand icon (+) and nothing happens), check the name of the computer hosting the report server. If the computer name includes an underscore, toggle items do not work. This is a known issue. There is no workaround. If you want to support toggle items, you must use a computer that does not include underscore characters in its name.
Export to Web archive uses cached data
If you export a report to Web archive (MHTML) in Microsoft Internet Explorer, and you select a different parameter value between export operations, the exported report will contain the report values associated with the previous selection. This occurs because Internet Explorer loads the report from its cache rather than the up-to-date version provided by the report server. To work around this issue, you can either clear the browser cache or click Refresh on the report toolbar before re-exporting the report.
For information about other browser-related issues, see Browser Support in Reporting Services.
Export fails if you are missing a the corresponding client application
Some export formats require a client application. If a required client application is not installed, the export does not occur. For example, if you want to open a report in PDF format, you must have Adobe Acrobat Reader installed on your computer.
Interactive report features do not work when exported to a static file
If you save a report that has interactive features, such as drilldown matrix reports and reports that include hyperlinks, as a static file, those features do not work.
If you save a report in an interactive format (specifically, HTML with Office Web Components) onto your computer, the resulting file will contain errors and missing images. The HTML with Office Web Components format is not intended for static files.
Images and Charts Do Not Load When Using Run As To Run a Report
You can use the Microsoft Windows Run As command to view a report using a different security context. In some circumstances, reports that include charts might not load correctly. The report server caches charts as temporary Internet files when you open the report. If you do not have permission to access the folders that contain the cached files, the charts might be missing from the report.
Help and Information
17 November 2008
14 April 2006