Troubleshooting unreadable snapshots in SQL Server Reporting Services

Snapshot reports are convenient because they can be generated quickly, created automatically on a schedule, and they don't consume many server resources when generated. These reports are stored in a temporary directory named "RSTempFiles," usually located in \Program Files\Microsoft SQL Server\MSSQL\Reporting Services. Sometimes, however, a problem occurs when a generated snapshot is only viewable once. Whenever someone tries to view it after that, an error is generated. Usually the error is along the lines of:

(The exact name of the file varies because it's randomly generated with each snapshot, but the basic error is the same.)

This error may be caused by a problem with RSTempFiles directory permissions. Normally the ASP.NET and SYSTEM users have every level permissions over the directory, with the exception of Full Control. Problems arise when the login used by the Reporting Services service doesn't have the same level of control as the users. For instance, you might have this issue if you changed the way services run for the sake of security (i.e., running them in a user account with reduced privileges).

Usually, services are set to run in the context of the Local System Account, but some administrators (and some security configuration packages) prefer to run some services in a more r...

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT SQL Server Business Intelligence (BI) and Data Warehousing Programming report generation with SQL Server Reporting Services 2008 Using the Pivot transformation in SQL Server Integration Services DBA career paths could lead to business intelligence Are data warehouses made for the cloud? Q&A: Business intelligence gets a facelift in SQL Server 2008 R2 Project Gemini gets a new name, Madison earns buzz Speed up reports in SQL Server Reporting Services with caching Data Transformation Services vs. SSIS: The key differences Using package configurations in SQL Server Integration Services (SSIS) How SQL Server 2008 components impact SharePoint implementations Database Management and Administration Password cracking tools for SQL Server Using traces in SQL Server Profiler Meet compliance requirements with improved database security practices Hardening the network and OS for SQL Server security Securing the server and database in SQL Server How SQL Server 2008 components impact SharePoint implementations Troubleshooting Distributed Transaction Coordinator errors in SQL Server Achieving high availability and disaster recovery with SharePoint databases Clearing the Windows page file and its effect on server performance Deploying a SQL Server virtual appliance for Microsoft Hyper-V

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary data aggregation  (SearchSQLServer.com) data preprocessing  (SearchSQLServer.com) data warehouse  (SearchSQLServer.com) FileMaker  (SearchSQLServer.com) GIS  (SearchSQLServer.com) MOLAP  (SearchSQLServer.com) pivot table  (SearchSQLServer.com) Quiz: SQL Server 2000  (SearchSQLServer.com) SQL  (SearchSQLServer.com) T-SQL  (SearchSQLServer.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

estrictive context just in case. You can determine the context the service is using by launching the Services snap-in from Administrative Tools, double-clicking on the name of the service and selecting the Log On tab.

One way to work around this issue without too much risk or confusion is to set the Everyone group to have the Read permission for that directory. This insures that no matter what user context the Reporting Services service is running in, it'll be able to read that directory.

About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter. Check it out for the latest advice and musings on the world of Windows network administrators -- and please share your thoughts as well!

More information from SearchSQLServer.com