Locating SSRS log files is often the first critical step when troubleshooting rendering failures, subscription errors, or performance issues in SQL Server Reporting Services. These files provide a detailed chronological record of server activity, including report processing, data retrieval, and authentication events, making them indispensable for diagnosing problems. Understanding the default paths and configuration nuances is essential for any administrator or developer responsible for maintaining a healthy reporting environment.
Default Installation Paths for SSRS Log Files
The location of SSRS log files depends heavily on the version of SQL Server and the operating system architecture. For the most common scenarios on Windows Server, the primary log directory is consistently found within the installation root. This standardized structure ensures that diagnostic data is stored in a predictable location, simplifying administrative tasks and automation scripts.
SQL Server 2016, 2017, 2019, and 2022
For modern installations, the log files are stored in a directory specific to the instance name. If you are using the default instance, the path is straightforward and does not require navigating through complex instance-specific folders. The structure is designed to separate configuration data from operational logs, reducing the risk of accidental modification.
C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles
C:\Program Files\Microsoft SQL Server\MSRS14.MSSQLSERVER\Reporting Services\LogFiles
C:\Program Files\Microsoft SQL Server\MSRS15.MSSQLSERVER\Reporting Services\LogFiles
C:\Program Files\Microsoft SQL Server\MSRS16.MSSQLSERVER\Reporting Services\LogFiles
SQL Server 2012 and 2014
While the underlying architecture remains similar, the version numbering in the file path differs to reflect the major release cycle. Administrators working with these older, but still supported, versions will find the logs in a nearly identical structure, requiring only a slight adjustment in the directory name to locate the correct files.
C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\LogFiles
C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\LogFiles
Configuring the Log File Settings
While the default location is reliable, you might need to change the logging level or the physical path for specific troubleshooting needs or disk space management. The configuration is handled through the rsreportserver.config file, which acts as the central registry for all SSRS runtime behavior. Modifying this file allows you to tailor the logging detail to match the severity of the issue you are investigating.
To adjust the settings, you must locate the rsreportserver.config file, typically found in the same installation directory as the logs, specifically in the \Reporting Services\ReportServer folder. Within this XML file, the section contains a entry where you can define the maximum file size and the retention policy for archived logs. Increasing the logging verbosity to "All" can be crucial for capturing granular error details during a critical failure, though it will generate larger file sizes.
Identifying and Rotating Log Files
SSRS log files are generated with specific naming conventions that include timestamps and identifiers for the reporting server process. The primary active log is usually named simply "LogFile.log," while archived logs are appended with date stamps and numeric suffixes. This rotation mechanism prevents a single log file from growing indefinitely and consuming all available disk space on the server volume.
