Reporting Services Trace Logs
Trace logs contain highly detailed information about report server operations. Trace logs include redundant information that is recorded in other log files, plus additional information that is not otherwise available. Trace logs are useful if you are debugging an application that includes a report server, or investigating a specific problem that was written to the event log or execution log.
Finding Trace Logs
Reporting Services provides three trace log files, which are located at \Microsoft SQL Server\<SQL Server Instance>\Reporting Services\LogFiles. They are described in the following table.
| Log file name | Description |
|---|---|
| ReportServerService_<timestamp>.log | Trace log for the Report Server Windows service and Web service. |
| ReportServerWebApp_<timestamp>.log | Trace log for Report Manager. |
| ReportServer_<timestamp>.log | Trace log for the report server engine. |
Viewing Log Information
Trace logs are text files. You can use any text editor to view a log. The following information can be found in a trace log:
- System information, including operating system, version, number of processors, and memory.
- Reporting Services component and version information.
- Events logged the Application log.
- Exceptions generated by the report server.
- Low resource warnings logged by a report server.
- Inbound SOAP envelopes and summarized outbound SOAP envelopes.
- HTTP header, stack trace, and debug trace information.
You can review trace logs to determine whether a report delivery occurred, who received the report, and how many delivery attempts were made. Trace logs also record report execution activity and the environment variables that are in effect during report processing. Errors and exceptions are also entered into trace logs. For example, you may find report timeout errors (indicated as a ThreadAbortExceptions entry).
Managing Log File Content
Trace logs are created daily, starting with the first entry that occurs after midnight (local time). The local time of the computer is used for naming the trace log. By default, trace logs are deleted after fourteen days. You can determine how long the files are kept by setting the KeepFilesForDays configuration setting. For more information about configuration settings that affect tracing, see ReportingServicesService Configuration File. Tracing configuration settings can also be found in the \ReportManager\Web.config and \ReportServer\Web.config files.
See Also
Checking Reporting Services Log Files
