Export (0) Print
Expand All

RSWebApplication Configuration File

SQL Server 2005

Updated: 17 July 2006

The RSWebApplication.config file stores configuration settings for Report Manager. It specifies settings used for report distribution and the number of open connections per user.

This file is located in the \Reporting Services\ReportManager folder.

You can edit this file to limit the number of open connections, change the default delivery extension, and change the default rendering format for each delivery extension.

The following example shows some of the settings and default values found in the RSWebApplication.config file.

<Configuration>
     <UI>
     <ReportServerUrl></ReportServerUrl>
     <ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>
     <ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
     </UI>
     <Extensions>
          <DeliveryUI>
               <Extension Name="Report Server Email" Type="Microsoft.ReportingServices.EmailDeliveryProvider.EmailDeliveryProviderControl,ReportingServicesEmailDeliveryProvider">
                    <DefaultDeliveryExtension>True</DefaultDeliveryExtension>
                    <Configuration>
                         <RSEmailDPConfiguration>
                              <DefaultRenderingExtension>MHTML</DefaultRenderingExtension>
                         </RSEmailDPConfiguration>
                    </Configuration>
               </Extension>
               <Extension Name="Report Server FileShare" Type="Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareUIControl,ReportingServicesFileShareDeliveryProvider"/>
          </DeliveryUI>
     </Extensions>
     <Add Key="MaxActiveReqForOneUser" Value="20"/>
     <Add Key="DisplayErrorLink" Value="true"/>
</Configuration>

This example shows you how to use ReportServerUrl instead of ReportServerVirtualDirectory.

ms155878.note(en-US,SQL.90).gifImportant:
Configuration settings are case-sensitive. When adding new entries, be sure to type the setting exactly as shown. If you use the wrong case, you will get an error similar to "The configuration file contains an element that is not valid. The ElementName element is not a configuration file element."

<UI>
     <ReportServerUrl>http://www.adventure-works.com/ReportServer</ReportServerUrl>
     <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
     <ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>

The following table provides information about the default settings. Settings are presented in the order in which they appear in the configuration file. If you are using custom delivery extensions, your configuration file will include additional settings.

Setting Description

ReportServerVirtualDirectory

Specifies the SOAP endpoint of the report server that is used by Report Manager. The value is the report server virtual directory name. For example, if the report server URL is http://adventure-works.com/reportserver, the value for the ReportserverVirtualDirectory setting is reportserver.

This setting requires that Report Manager and report server be configured to use the same Web site. If they use different Web sites, delete the value for ReportServerVirtualDirectory and use ReportServerURL instead.

For more information about URLs and this setting, see Configuring Report Server Virtual Directories and Configuring a Report Server for Internet Access.

ReportServerUrl

Provides an alternative way to specify the SOAP endpoint of the report server that is used by Report Manager. You can use this setting instead of ReportServerVirtualDirectory when Report Manager and the report server virtual directories are hosted on separate servers or Web sites, or if you need to specify a fully qualified domain name for the report server.

ReportServerURL and ReportServerVirtualDirectory are mutually exclusive. If you specify ReportServerURL, you must delete the entry for ReportServerVirtualDirectory.

To specify this setting, you must edit the RSWebApplication.config file manually. Valid values include http://<server>/<reportserver> or https://<server>/<reportserver> if you are using certificates. If Report Manager is installed separately on an Internet-facing Web server, this value must be a fully-qualified domain name that can be used to access a report server instance behind the firewall. This value can never be set to localhost.

If a Secure Sockets Layer (SSL) certificate is installed, this value must be the name of the server that is registered for that certificate. If you get the error "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel", set ReportServerUrl to the fully-qualified domain name of the server for which the certificate was issued. For example, if the certificate is registered to https://adventure-works.com.onlinesales, the report server URL would be https://adventure-works.com.onlinesales/reportserver.

To view an example of how this setting is used, see the example provided in this topic. For more information about URLs and this setting, see Configuring Report Server Virtual Directories.

ReportBuilderTrustLevel

Specify whether Report Builder is launched in full trust or partial trust. Valid values are FullTrust and PartialTrust. The default is FullTrust. For more information about these trust levels, see Starting Report Builder.

PassThroughCookies

This setting is not included in the configuration file by default. To use it, you must add it manually.

This setting configures Report Manager to transmit custom authentication cookies. For more information and to view and example of how to specify the configuration settings, see Configuring Report Manager to Pass Custom Authentication Cookies

ReportServerExternalUrl

This setting is no longer used. In previous releases, it was used to provide a fully qualified report server URL to applications and internal processes that needed to send requests to a report server behind a firewall. This setting was not included in the configuration file by default. If you added it manually, you can either leave it in the file or remove it. Note that deploying Report Builder on an Internet-facing report server is an untested deployment scenario in this release. If you used this setting in the past to support Internet access to Report Builder, you should consider an alternative strategy.

DeliveryUI

Specifies the delivery extensions that can be used with subscriptions. The extension names that you specify in this section appear as delivery options in the subscription definition pages in Report Manager. Reporting Services includes two default delivery extensions for subscriptions: Report Server Email and Report Server FileShare. For more information, see Configuring a Report Server for E-Mail Delivery and File Share Delivery in Reporting Services.

DefaultDeliveryExtension

Specifies whether a delivery extension is the default. Report Server E-Mail is the default delivery extension. Valid values include True or False. If more than one extension contains a value of True, the first extension is considered the default extension.

Configuration

Specifies configuration options for a delivery extension. You can set a default rendering format for each delivery extension. Valid values are the rendering extension names noted in the render section of the rsreportserver.config file.

MaxActiveReqForOneUser

Specifies the maximum number of simultaneous and in-progress connections that a single user can open to Report Manager. Once the limit is reached, further connection requests from the user are denied. This configuration setting is intended to mitigate a denial of service attack.

Valid values are 0 to a maximum integer. 0 indicates no limit on the number of connections. The default is 20.

Note that most requests process very quickly so it is unlikely that a single user will have more than 20 open connections at any given time. If users are opening more than 15 process-intensive reports at the same time, you might need to increase this value.

DisplayErrorLink

Displays a link to the Microsoft Help and Support site. This link appears in error messages. Users can link to the site to view updated error message content. Valid values include true or false. The default is true.

Release History

17 July 2006

New content:
  • Added an example that shows how to specify ReportServerUrl.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft