Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Recommended configuration for Verbose Logging in Reporting Services

Recommended configuration for Verbose Logging in Reporting Services

Summary

Verbose Logging can be enabled to provide fine grain information within the RS Trace Log file.  As a result of this logging level, the log file could become very large depending on the load of the Report Server.  This information can be very useful when troubleshooting certain scenarios, however it is not recommended to leave the RS Trace Log settings to be in verbose mode.   If verbose logging is enabled, you should disable it if no longer needed to troubleshoot your issue.

By default, the RS Trace Log file is not configured for verbose output.

↑ Back to the top

More Information

The default location for ReportingServicesService.exe.config is C:\Program Files\Microsoft SQL Server\MSRS10.<Instance Name>\Reporting Services\ReportServer\bin for SQL Server 2008 and C:\Program Files\Microsoft SQL Server\MSRS10_50.<Instance Name>\Reporting Services\ReportServer\bin for SQL Server 2008 R2.

A setting of 4 for both the DefaultTraceSwitch value and the Components/all value, will place the logging level in verbose mode.  For normal operation, these two values should be set back to a value of 3.

  <system.diagnostics>
    <switches>
      <add name="DefaultTraceSwitch" value="4" />
    </switches>
  </system.diagnostics>
  <RStrace>
    <add name="FileName" value="ReportServerService_" />
    <add name="FileSizeLimitMb" value="32" />
    <add name="KeepFilesForDays" value="14" />
    <add name="Prefix" value="appdomain, tid, time" />
    <add name="TraceListeners" value="file" />
    <add name="TraceFileMode" value="unique" />
    <add name="HttpTraceFileName" value="ReportServerService_HTTP_" />
    <add name="HttpTraceSwitches" value="date,time, clientip,username,serverip,serverport,host,method,uristem,uriquery,protocolstatus,bytesreceived,timetaken,protocolversion,useragent,cookiereceived,cookiesent,referrer" />
    <add name="Components" value="all:4,reportrendering:4,http:4" />
  </RStrace>

For further information regarding the RS Trace Log file in Reporting Services please refer to the Books Online documentation - http://technet.microsoft.com/en-us/library/ms156500.aspx.

For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table:

 

Rule software

Rule title

Rule description

Product versions against which the rule is evaluated

SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA)

Verbose logging is enabled

The SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to detect when Verbose Logging is enabled.  The SQL Server 2008 R2 BPA supports both SQL Server 2008 and SQL Server 2008 R2. If you run the BPA tool and encounter a Warning with the title of Reporting Services - Verbose logging is enabled, this means that the verbose logging values are present in your configuration file for the given Reporting Services Instance.

The BPA rule looks at the first Add tag within System.Diagnostics/Switches within the ReportingServicesService.exe.config files.  It then looks at the value for that tag and checks if it is a value of 4.  If it is a value of 4, we will then go through the different Components.  If any of the components have a value of 4, the rule will fire. 

Note:  The rule will ignore the http component.

Note:  If you placed an additional Add tag entry above the DefaultTraceSwitch, it may create a false positive for this rule.

SQL Server 2008
SQL Server 2008 R2

SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA)

Verbose logging is enabled

The SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) provides a rule to detect when Verbose Logging is enabled. If you run the BPA tool and encounter a Warning with the title of Reporting Services - Verbose logging is enabled, this means that the verbose logging values are present in your configuration file for the given Reporting Services Instance.

The BPA rule looks at the first Add tag within System.Diagnostics/Switches within the ReportingServicesService.exe.config files.  It then looks at the value for that tag and checks if it is a value of 4.  If it is a value of 4, we will then go through the different Components.  If any of the components have a value of 4, the rule will fire. 

Note:  The rule will ignore the http component.

Note:  If you placed an additional Add tag entry above the DefaultTraceSwitch, it may create a false positive for this rule.

 SQL Server 2012

  

↑ Back to the top

Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2146315
Revision : 1
Created on : 1/8/2017
Published on : 4/3/2012
Exists online : False
Views : 127