Where is rswebapplication.config

For more information about how to modify a configuration file or to learn more about how the report server reads new and updated configuration settings, see Modify a Reporting Services Configuration File RSreportserver. That file is now obsolete.

If you upgraded from a previous installation, the file will not be deleted but the report server will not read any settings from it. If the file exists on your computer, you should delete it. Summary of Configuration Files Native Mode.

The following table provides a description of where configuration settings are stored. Most configuration settings are stored in configuration files that are included with Reporting Services. By default, the installation directory is the following:. The following table provides a description of configuration files used for a SharePoint mode report server. Backup and Restore Operations for Reporting Services. Among other things, including the encryption keys , master keys , Backing Up the Configuration Files.

I have just installed SQL Server Reporting Services, migrated all databases and reports , including all folder permissions , from a previous server sql server ,and all is working fine. However, on the backup strategy, I cannot find some of the. The file that is missing is Rsmgrpolicy. Everything is working fine, including the encryption and all the security, so as the file is not there, I will not need to include it on my backups.

Reporting Services Configuration Files. Stores the code access security policies for the web portal. It was not clear in the first documentation but all is good now. Sign up to join this community. The best answers are voted up and rise to the top.

It also contains system and item properties, and permissions for accessing report server content. If your migration includes using a different [!

If you are using the same [! Choose the [! SQL Server Reporting Services requires that you use one of the following versions to host the report server database:. Start [! Create the RSExecRole in the system databases if the [!

Remember that both the report server database and the temporary database are interdependent and must be moved together. Do not copy the databases; copying does not transfer all of the security settings to the new installation.

The report server recreates these jobs automatically. If your installation includes custom report items, assemblies, or extensions, you must redeploy the custom components.

If you are not using custom components, skip to section Configure the Report Server. Custom security extensions must be rewritten using the IAuthenticationExtension2 interface. Custom rendering extensions for [! HTML 3. In SQL Server, the report server binaries are located in the following location for the default report server instance:.

Modify the configuration files to add entries for your custom component. The entries vary depending on the kind of assembly you are using. For instructions on where to place files and add configuration entries, see below:. Deploying a Custom Assembly. How to: Deploy a Custom Report Item. Deploying a Data Processing Extension. Deploying a Delivery Extension.

Deploying a Rendering Extension. Implementing a Security Extension. Configure URLs for the Report Server Web service and web portal, and configure the connection to the report server database. If you are migrating a scale-out deployment, take all of the report server nodes offline and migrate each server one at a time. Once the first report server is migrated and it successfully connects to the report server database, the report server database version is automatically upgraded to the SQL Server database version.

IMPORTANT] If any of the report servers in the scale-out deployment are online and have not been migrated, they might encounter an rsInvalidReportServerDatabase exception because they are using an older schema when connected to the upgraded.

If the report server you migrated is configured as the shared database for a scale-out deployment, you need to delete any of the old encryption keys from the Keys table in the ReportServer database, before configuring the report server service. If the keys are not removed, the migrated report server will try to initialize in scale-out deployment mode. Finally, the following line in RSReportServer.

Acceptable values are:. Please also provide the following information and we will be glad to follow up:. Thank-you for your reply to this. I've already tried most of what you suggested except for two points: I have SecureConnectionLevel set to 3 rather that 2 and I'm not sure I matched the case of the URL exactly.

I'll double check everything. I made the changes to the RSReportServer. However, the Help link still point to http instead of https. Do you have any problem with your help link? I was just wondering if this makes a different.

Thanks, Monica. Thanks for replying. I've already found the loopback check and disabled it. Everything worked fine after that. I won't have access to that machine for a few days but I'll try to remember and check once I get access again. I've had "SecureConnectionLevel" set to both 2 and 3 during the course of my troubleshooting.

I don't think it will make a difference for this issue. I have the same problem as described in the first post. To solve this, I tried all your solutions, but non worked. I also implemented custom authentication and authorisation. After changing the custom authentication different domain name in the cookie everything worked.