Modify a Reporting Services Configuration File (RSreportserver.config)
Reporting Services stores application settings in a set of configuration files. Setup creates the configuration files for each report server instance you install. Within each file, values are either set during installation or when you use tools and applications to configure a server for operation. In some cases, you must modify a file directly to add or configure advanced settings. Configuration settings are specified as either XML elements or attributes. If you understand XML and configuration files, you can use a text or code editor to modify user-definable settings.
Some configuration settings can be set only through a tool. Settings that contain encrypted values must be modified through the Reporting Services Configuration tool, the Setup program, or the rsconfig command line utility. You must be a member of the local Administrators group to run these tools.'
Use caution when modifying configuration files. If you modify a setting that is reserved for internal use, you may disable your installation. Generally, modifying configuration settings is not recommended unless you are trying to solve a specific problem. For more information about which settings are safe to change, see RsReportServer.config Configuration File or RSReportDesigner Configuration File. For more information about configuration files, see the Microsoft.NET Framework product documentation.
In this topic:
Reading and Using Configuration Values
A report server reads the configuration files when the service starts and whenever the configuration file is saved. New and revised values take effect in a new application domain after the current application domain expires. Whenever possible, requests that are still processing in the current application domain are allowed to complete. However, a few settings require an immediate application domain recycle operation. In this case, all requests that are in process are restarted in a new application domain.
If the report server detects an invalid value, the report server logs an error to the Windows application log and either fails to start or uses a default value, depending on the error:
If the error is malformed XML, the report server will not start. If the report server is running when you introduce the error, the report server ignores the invalid configuration file until the report server restarts or the application domain is recycled. Once the error is detected, the report server will no longer start.
If the error is an invalid configuration value, the server will use internal default values and log an error to the trace log files. In the few cases where internal default values are not available, the server will return the rsServerConfigurationError error if the invalid configuration setting is critical to server operations. Errors about missing or invalid critical settings are returned to the client application in an HTML error page and logged to the event log.
All configuration file changes, including successful changes, are recorded in the report server trace log file. Only errors are logged to the application event log.
About Default Values
Most configuration settings have default values that are specified internally in the report server. The report server will use these values if a user-defined value is invalid or not specified. If a default value must be used due to an invalid configuration setting, an error is written to the trace log file.
Deleting Configuration Settings
For configuration settings that have default values, removing the setting from the configuration file has no effect. Most configuration settings are actually defined and configured internally. If you delete an item from the configuration file, the internal copy is still available and uses the default value that is defined for it.
To Edit a Reporting Services Configuration File
Find the configuration file you want to edit:
RSReportServer.config is located in the following folder:
C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\ReportServer
Applies to: January 2017 Technical Preview of Power BI reports in SQL Server Reporting Services
C:\Program Files\Microsoft SQL Server Reporting Services\RSServer\ReportServer
RSReportServerServices.exe.config is located in the following folder:
This is not available with the January 2017 Technical Preview of Power BI reports in SQL Server Reporting Services.
C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\ReportServer\bin
RSReportDesigner.config is located in the following folder:
C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies
Save a copy of the file in case you need to roll back your changes.
Open the original file in Notepad or a code editor. Do not use Textpad; it sets the file length before the file is saved, causing an invalid character error to be written to the trace log file.
Type the element or value that you want to add or use. Elements are case-sensitive. If you are adding an element, be sure to use the correct upper and lower case letters. Specific instructions for editing configuration files are available if you are customizing rendering extension, authentication extensions, or data processing extensions:
Save the file.
Check the trace log files to verify that errors did not occur. If you see error conditions, a setting or its value is specified incorrectly. Review the RsReportServer.config Configuration File for valid values for any setting that is causing an error. For more information about how to view the trace log, see Report Server Service Trace Log.
RsReportServer.config Configuration File
ReportingServicesService Configuration File
RSReportDesigner Configuration File
Deploying a Data Processing Extension
Deploying a Delivery Extension
Deploying a Rendering Extension
Reporting Services Configuration Files