Critical error pwm uninitialized

RsReportServer.config Configuration File

The Reporting ServicesRsReportServer.config file stores settings that are used by the Report Server Web service and background processing. All Reporting Services applications run within a single process that reads configuration settings stored in the RSReportServer.config file. Both Native mode and SharePoint mode report servers use the RSReportServer.config, however the two modes don’t use all of the same settings in the configuration file. The SharePoint mode version of the file is smaller as many of the settings for SharePoint mode are stored in SharePoint configuration databases rather than the file. This topic describes the default configuration file that is installed for Native mode and SharePoint mode and some of the important settings and behaviors that are controlled by the configuration file.

In SharePoint mode, the configuration file contains those settings that apply to all service application instances running on that computer. The SharePoint configuration database contains configuration settings that apply to specific service applications. The settings that are stored in the Configuration database and managed through the SharePoint management pages can be different for each Reporting Services service application.

The settings are presented in following content in the order in which they appear in the configuration file that is installed by default. For instructions on how to edit this file, see Modify a Reporting Services Configuration File (RSreportserver.config).

File Location

The RSReportServer.config is located in the following folders, depending on the report server mode:

Native mode report server

Applies to: SQL Server Reporting Services (2016)

Applies to: SQL Server Reporting Services (2017 and later)

Applies to: Power BI Report Server

SharePoint mode report server

Reporting Services integration with SharePoint is no longer available after SQL Server 2016.

General Configuration Settings (rsreportserver.config)

The following table provides information about general configuration settings that appear in the first part of the file. Settings are presented in the order in which they appear in the configuration file. The last column of the table indicates if the setting applies to a Native mode report server (N) or a SharePoint mode report server (S) or both.

In this topic, «maximum integer» refers to INT_MAX value of 2147483647. For more information, see Integer Limits (https://msdn.microsoft.com/library/296az74e(v=vs.110).aspx).

The following is an example of SharePoint mode:

MSRS12.@Sharepoint N,S InstallationID An identifier for the report server installation that Setup creates. This value is set to a GUID. Don’t modify this setting. N SecureConnectionLevel Specifies the degree to which Web service calls must use Transport Layer Security (TLS), previously known as Secure Sockets Layer (SSL). This setting is used for both the Report Server Web service and the web portal. This value is set when you configure a URL to use HTTP or HTTPS in the Reporting Services Configuration tool. In SQL Server 2008 R2, SecureConnectionLevel is made an on/off switch. For earlier versions than SQL Server 2008 R2 the valid values range are from 0 through 3, where 0 is least secure. For more information, see ConfigurationSetting Method — SetSecureConnectionLevel, Using Secure Web Service Methods and Configure TLS Connections on a Native Mode Report Server. N,S DisableSecureFormsAuthenticationCookie Default value is False.

Specifies whether to disable the forcing of the cookie used for form and custom authentication to be marked secure. Starting with SQL Server 2012, Reporting Services will automatically mark forms authentication cookies used with custom authentication extensions, as a secure cookie when sent to the client. When report server administrators and custom security extension authors change this property, they can revert to the previous behavior, which allowed the custom security extension author to determine whether to mark the cookie as a secure cookie. It’s recommended that secure cookies are used for forms authentication to help prevent network sniffing and replay attacks. N CleanupCycleMinutes Specifies the number of minutes after which old sessions and expired snapshots are removed from the report server databases. Valid values range from 1 to maximum integer. The default is 10. N,S MaxActiveReqForOneUser Specifies the maximum number of reports that one user can process at the same time. Once the limit is reached, further report processing requests are denied. Valid values are 1 to a maximum integer. 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.

This setting is ignored for report servers that run in SharePoint integrated mode. N,S MaxActiveReqForAnonymous Specifies the maximum number of anonymous requests that can be in process at the same time. Once the limit is reached, further processing requests are denied. Valid values are 1 to a maximum integer. The default is 200. DatabaseQueryTimeout Specifies the number of seconds after which a connection to the report server database times out. This value is passed to the System.Data.SQLClient.SQLCommand.CommandTimeout property. Valid values range from 0 to 2147483647. The default is 120. A value of 0 specifies an unlimited wait time and therefore is not recommended. N AlertingCleanupCycleMinutes The default is 20.

Determines how often the cleanup of temporary data stored in the Alerting database occurs. S AlertingDataCleanupMinutes The default is 360.

Determines how long session data used for creating or editing an alert definition is retained within the Alerting database. Default is 6 hours. S AlertingExecutionLogCleanupMinutes The default is 10080.

Determines how long to keep Alerting execution log values. Default is 7 days. S AlertingMaxDataRetentionDays The default is 180.

Determines how long to keep alert data required to prevent duplicate alert messages when the data for the alert has not changed. S RunningRequestsScavengerCycle Specifies how often orphaned and expired requests are canceled. This value is specified in seconds. Valid values range from 0 to maximum integer. The default is 60. N,S RunningRequestsDbCycle Specifies how often the report server evaluates running jobs to check whether they have exceeded report execution time outs, and when to present running job information in the Manage Jobs page of the web portal. This value is specified in seconds. Valid values range from 0 to 2147483647. The default is 60. N,S RunningRequestsAge Specifies an interval in seconds after which the status of a running job changes from new to running. Valid values range from 0 to 2147483647. The default is 30. N,S MaxScheduleWait Specifies the number of seconds the Report Server Windows service waits for a schedule to be updated by SQL Server Agent service when Next Run Time is requested. Valid values range from 1 to 60.

In the default configuration file, MaxScheduleWait is set to 5.

If the report server cannot find or read the configuration file, the server defaults MaxScheduleWait to 1. N,S DisplayErrorLink Indicates whether a link to the Microsoft Help and Support site is displayed when errors occur. This link appears in error messages. Users can click the link to open updated error message content on the site. Valid values include True (default) and False. N,S WebServiceuseFileShareStorage Specifies whether to store cached reports and temporary snapshots (created by the Report Server Web service for the duration of a user session) on the file system. Valid values are True and False (default). If the value is set to false, temporary data is stored in the reportservertempdb database. N,S ProcessTimeout Specifies the number of seconds the report server Process Monitor will wait for any service activity operation to complete before stopping the service. Valid values range from 0 to maximum integer. The default is 150. This setting is disabled by default and can be enabled by removing the comment syntax ( ). N ProcessTimeoutGcExtension Specifies the number of seconds the report server Process Monitor will wait for a service activity operation to complete before stopping the service. This setting applies only if .NET Garbage Collection is in progress and the ProcessTimeout value was reached. Valid values range from 0 to maximum integer. The default is 30. This setting is disabled by default and can be enabled by removing the comment syntax ( ). N WatsonFlags Specifies how much information is logged for error conditions that are reported to Microsoft.

0x0430 = a full dump

0x0428 =a minidump

0x0002 = no dump N,S WatsonDumpOnExceptions Specifies a list of exceptions that you want to report in an error log. This is useful when you have a recurring issue and want to create a dump with information to send to Microsoft for analysis. Creating dumps affects performance, so change this setting only when you are diagnosing a problem. N,S WatsonDumpExcludeIfContainsExceptions Specifies a list of exceptions that you don’t want to report in an error log. This is useful when you are diagnosing a problem and don’t want the server to create dumps for a specific exception. N,S

URLReservations (RSReportServer.config file)

URLReservations defines HTTP access to the Report Server Web service and the web portal for the current instance. URLs are reserved and stored in HTTP.SYS when you configure the report server.

For SharePoint mode, URL reservations are configured in SharePoint Central Administration. For more information, see Configure alternate access mapping (https://technet.microsoft.com/library/cc263208(office.12).aspx).

Don’t modify URL reservations in the configuration file directly. Always use the Reporting Services Configuration Manager or the Report Server WMI provider to create or modify URL reservations for a Native mode report server. If you modify the values in the configuration file, you might corrupt the reservation, which will cause server errors at run time or leave orphan reservations in HTTP.SYS that are not removed if you uninstall the software. For more information, see Configure Report Server URLs (Report Server Configuration Manager) and URLs in Configuration Files (Report Server Configuration Manager).

URLReservations is an optional element. If it is not present in the RSReportServer.config file, the server might not be configured. If it is specified, all child elements except for AccountName are required.

The last column of the table indicates if the setting applies to a Native mode report server (N) or a SharePoint mode report server (S) or both.

Authentication (RSReportServer.config file)

Authentication specifies one or more authentication types accepted by the report server. The default settings and values are a subset of the settings and values that are possible for this section. Only the default settings are added automatically. To add other settings, you must use a text editor to add the element structure to the RSReportServer.config file and set the values.

Default values include RSWindowsNegotiate and RSWindowsNTLM with EnableAuthPersistance set to True:

All other values must be added manually. For more information and examples, see Authentication with the Report Server.

The last column of the following table indicates if the setting applies to a Native mode report server (N) or a SharePoint mode report server (S) or both.

Service (RSReportServer.config file)

Service specifies the application settings that apply to the service as a whole.

The last column of the following table indicates if the setting applies to a Native mode report server (N), a SharePoint mode report server (S), or Power BI Report Server (P).

UI (RSReportServer.config file)

UI specifies configuration settings that apply to the web portal application.

The last column of the following table indicates if the setting applies to a Native mode report server (N) or a SharePoint mode report server (S) or both.

Extensions (RSReportServer.config file) Native Mode

The Extensions section appears in the rsreportserver.config file only for native mode report servers. Extension information for SharePoint mode report servers is stored in the SharePoint configuration database and is configured per Reporting Services service application.

Extensions specifies configuration settings for the following extensible modules of a Reporting Services installation:

Источник