Turn on Reporting Services events for the SharePoint trace log (ULS)

Beginning with SQL Server 2008 R2 (10.50.x), Reporting Services servers in SharePoint mode can write Reporting Services events to the SharePoint Unified Logging Service (ULS) trace log. Reporting Services specific categories are available on the Monitoring page of SharePoint Central Administration.

In this article:

• General ULS log recommendations

• Turn on and off Reporting Services events in the Reporting Services category

• Recommended configuration

• Reading the logs entries

• List of SQL Server Reporting Services events

• View a log file with PowerShell

• Trace log location

The following table lists event categories and levels that are recommended for monitoring a Reporting Services environment. When an event is logged, each entry includes the time the event was logged, the process name, and the thread ID.

1. From SharePoint Central Administration, select Monitoring.

2. Select Configure Diagnostic Logging in the Reporting group.

3. Find SQL Server Reporting Services in the category list.

4. Select the plus symbol (+) to expand the sub categories under SQL Server Reporting Services.

5. Choose the subcategories to be added to the trace log.

6. At the bottom of the categories list, select an event level for the Least critical event to report to the trace log. Select None to disable tracing.

The following logging options are recommended as a standard configuration:

• HTTP Redirector

• SOAP Client Proxy

• If you're experiencing issues with configuration, add Configuration Pages.

You can review all of the current farm diagnostic log settings with the following PowerShell cmdlet:

Get-SPDiagnosticConfig  

The Reporting Services entries in the log are formatted in the following way.

• Product:SQL Server Reporting Services
• Category: Events related to the server have the characters Report Server at the beginning of the name. For example, Report Server Alerting Runtime. These events are also logged to the report server log files.
• Category: Events related to or communicated from a web front-end component don't contain Report Server, for example, Report Server Alerting Runtime. The WFE entries do contain a CorrelationID but the server entries don't.

The following table is a list of the events in the SQL Server Reporting Services category:

You can use PowerShell to return a list of the Reporting Services related events from a ULS Log file. Enter the following command from the SharePoint 2010 Management Shell to return a filtered list of rows from the file a ULS log file UESQL11SPOINT-20110606-1530.log that contains sql server reporting services:

Get-content -path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\UESQL11SPOINT-20110606-1530.log" | select-string "sql server reporting services"  

There are also tools you can download that allow you read ULS logs. For example, the SharePoint LogViewer, available on GitHub.

For more information on how to use PowerShell to view log data, see View diagnostic logs (SharePoint Server 2010)

The trace log files are found in the folder c:\Program Files\Common files\Microsoft Shared\Web Server Extensions\14\logs but you can verify or change the path from the Diagnostic Logging page in SharePoint Central Administration.

For more information and steps to configure diagnostic logging on a SharePoint server in SharePoint 2010 Central Administration, see Configure diagnostic logging settings (Windows SharePoint Services).

More questions? Try asking the Reporting Services forum