Expand your skills. Get new features first. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help.
Can you help us improve? Resolved my issue. Clear instructions. These shared settings are documented first. Descriptions of extension-specific settings follow in a second table. File Share delivery sends a report that has been exported to an application file format to a shared folder on the network.
This delivery extension must be configured before it can be used. Report Server Document Library sends a report that has been exported to an application file format to a document library. This delivery extension can only be used by a report server that is configured to run in SharePoint integrated mode.
The NULL delivery provider is used to preload the cache with pre-generated reports for individual users. There are no configuration settings for this delivery extension. Specifies delivery extensions that contain a user interface component that appears in the subscription definition pages used when defining individual subscriptions in the web portal. If you create and deploy a custom delivery extension that has user-defined options and you want to use the web portal, you must register the delivery extension in this section.
Delivery extensions used only in data-driven subscriptions or in SharePoint application pages do not have settings in this section. Do not modify this section unless you are deploying a custom rendering extension. For more information, see Implementing a Rendering Extension.
Starting with the SQL Server Deploying a Rendering Extension. Specifies default and possibly custom data processing extensions used to process queries. Default data processing extensions include the following:. Do not modify this section unless you are adding custom data processing extensions. For more information, see Implementing a Data Processing Extension. Specifies semantic query processing extension used to process report models. The semantic query processing extensions included with Reporting Services provide support for SQL Server relational data, Oracle, and Analysis Services multidimensional data.
Do not modify this section. Query processing is not extensible. Specifies a model generation extension used to create report models from a shared data source that is already published on a report server.
Model generation is not extensible. Specifies the authorization component used by Reporting Services. This component is used by the authentication extension registered in the Authentication element of the RSReportServer. Do not modify this section unless you are implementing a custom authentication extension.
For more information about adding custom security features, see Implementing a Security Extension. For more information about authorization, see Authorization in Reporting Services. Specifies the default and custom authentication extensions used by the report server. The default extension is based on Windows Authentication. Specifies a Report Definition Language RDL mode that enables you to help detect and restrict the use of specific types of report resources by individual tenants in a scenario where multiple tenants share a single Web farm of report servers.
MapTileServerConfiguration defines configuration settings for Microsoft Bing Maps Web Services that provides a tile background for a map report item in a report that is published on a report server. All child elements are required. More questions? Try the Reporting Services forum.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? In this article.
Specifies the connection string to the database server that hosts the report server database. This value is encrypted and is added to the configuration file when you create the report server database.
For SharePoint, the database connection information is taken from the SharePoint configuration database. Specifies the type of credentials that the report server uses to connect to the report server database.
Valid values are Default and Impersonate. Default is specified if the report server is configured to use a SQL Server login or the service account to connect to the report server database.
Impersonate is specified if the report server uses a Windows account to connect to the report server database. Stores the domain, user name, and password of a domain account that is used by a report server to connect to a report server database.
Values for LogonUser , LogonDomain , and LogonCred are created when the report server connection is configured to use a domain account.
An identifier for the report server instance. Report server instance names are based on SQL Server instance names. This value specifies a SQL Server instance name. Do not modify this setting. An identifier for the report server installation that Setup creates. This value is set to a GUID. This setting is used for both the Report Server Web service and the web portal. For earlier versions than SQL Server R2 the valid values range are from 0 through 3, where 0 is least secure.
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 , Reporting Services will automatically mark forms authentication cookies used with custom authentication extensions, as a secure cookie when sent to the client. By changing this property, report server administrators and custom security extension authors 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 is recommended that secure cookies are used for forms authentication to help prevent network sniffing and replay attacks. 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 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. 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.
The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server R2 SP 2, click the following article number to view the article in the Microsoft Knowledge Base:. The fix for this issue was first released in Cumulative Update For more information about how to obtain this cumulative update package for SQL Server R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:.
The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:.
For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:. For more information about how to obtain this cumulative update package for SQL Server R2, click the following article number to view the article in the Microsoft Knowledge Base:. To work around this issue, make some changes to the parameter orders or names, or add a dummy parameter. These changes will generate a new set of parameters that will result in a different hash value.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Need more help? Start and Stop the Report Server Service. Skip to main content. This browser is no longer supported.
Download Microsoft Edge More info.
0コメント