SQL Server Reporting Services Configuration Tool

By:   |   Comments (23)   |   Related: > Reporting Services Configuration


Installing SQL Server Reporting Services is just the first step in building the foundation for a solid Reporting Services instance.  The second step in the process is configuring Reporting Services to conform to the particulars of your environment.  These configurations are made to the RSServer.config file via the Reporting Services Configuration Tool.  This tool is quite similar in concept and practice to the Surface Area Configuration Tool that is utilized to configure the SQL Server Database Services instance post-install. 

The Reporting Services Configuration Tool is very simple to use and once you know what each form affords, you can make quick work of configuring Reporting Services.  However, if not properly used, the tool may also facilitate a quick path to subsequent hours of frustration and frenzied troubleshooting.  The purpose of this tip is to help you with the heavy lifting when it comes to the Reporting Services Configuration Tool.  I'll walk you step-by-step through the tool, explaining what each field is expecting, and what options exist within the tool to properly configure the various configuration files from within the structure of the Reporting Services Configuration tool. 

I do not know the subtleties of each of your domains, therefore there will be steps where you may need to do a little leg-work in collecting the necessary values in order to properly configure your environment.


Launching the configuration tool is quite simple.  The tool is installed as a component of SQL Server Reporting Services and is located under Microsoft SQL Server 2005\Configuration Tools\Reporting Services Configuration in the Start Menu.  When you initially launch the tool you'll be prompted to connect to an instance of SQL Server Reporting Services.  Enter the values that are reflective of the environment you wish to configure and continue. 

instance selection

The first form that is presented in the SQL Server Reporting Services Configuration Tool provides you with the basic information of the instance, and its status.  Along the left margin of the tool you'll see an overview of each category that you're able to configure (each category will have a separate form in the configuration tool).  The status for each category is displayed and the legend for these statuses are provided at the bottom of the tool. 

Left Pane of SQL Server Reporting Services Configuration Tool

server status

As you proceed through each category, you'll see the status pane on the left side of the Reporting Services Configuration tool change accordingly.  Let's now move onto the right pane of the tool and proceed through each category in depth.

Server Status

This is the first screen you'll encounter after logging into the tool.  This screen only allows you to view the instance you are connected to, and gives you control over the running status of the service.

report server status

Report Server Virtual Directory and Report Manager Virtual Directory

SQL Server Reporting Services' Report Server and Report Manager are ASP.NET applications that are accessed via a URL composed in the following manner:  http://server/website/virtual_directory (https://server/website/virtual_directory if the server in question is configured for Secure Sockets Layer (SSL).)  The server component can be a server name, fully-qualified domain name, or even localhost.  It all depends upon how you're planning on accessing Reporting Services. 

If Reporting Services will be accessed from here... Server Name component in URL will be:
Within your local network or Intranet The Server (DNS) name
Remotely via the Internet A fully-qualified domain name
Locally on the same server localhost

The virtual directory is the only component of the URL that you're able to configure within Reporting Services.  The default values are presented below.  Just as is the case with any defaults in SQL Server, if you're concerned about security I strongly suggest you avoid using the default values.

directory settings

You can also configure Reporting Services for SSL connections.  To do so, simply check the Require Secure Socket Layer (SSL) connections checkbox and enter the appropriate values into the drop-down supplied.

manager virtual directory settings

In addition to the virtual directory name, you are also able to assign the virtual directory to an existing website or a default website.  You are not able to create the website from with this tool.  If you do not wish to assign the virtual directory name to the default website you will need to configure a new website first via Internet Information Services (IIS) before proceeding.  You can use the same website for both Report Manager and Report Server. 

By default, anonymous access is disabled; the Reporting Services virtual directories are configured for intranet access only. In order to configure Reporting Services for Internet connections, you will need to modify the report server configuration files - specifically the RSWebApplication configuration file.  Configuration file modifications are outside the scope of this article, however.  For more information please review the detailed articles available from Microsoft TechNet that touch upon that subject:

Configuring Report Server Virtual Directories

How to: Configure Reporting Services to Use a Non-Default Web Site (Reporting Services Configuration)

Windows Service Identity

The Report Server Windows service runs under the account you appointed when installing SQL Server Reporting Services.  You can use this configuration tool screen to change that setting post-install.  As is the case with any of the SQL service accounts it is recommended you use the appropriate configuration tool to change security settings or stop services to ensure that any dependent settings are automatically changed as well.

service identity

Web Service Identity

By default the Report Server Web service runs under Network Service in IIS 6.0 and the ASP.NET account in IIS 5.0.  However, you can use the Reporting Services Configuration Tool to modify the Web service to fit your environment's requirements.  You are able to set up the application pools for both Report Server and Report Manager in this screen as well. 

web service identity

Database Setup

Installing SQL Server Reporting Services does not automatically create the databases that Reporting Services requires to function properly.  You are able to create a new ReportServer and ReportServerTemp databases from within this form.  Optionally, you can connect to an existing instance of these databases.  This is convenient when migrating Reporting Services instances to new hardware or upgrading existing instances of Reporting Services.

database connection

Below, we will take a look at each of the options for setting up or connecting to an existing instance of the Reporting Services databases available from this form

Connect:  Connect simply allows you to establish a connection to an existing instance of the ReportServer database.  Select a server name to connect to, and credentials with the necessary rights.

RightPane7 Connect

New:  If you wish to create a new instance of the ReportServer and ReportServerTemp databases select this option.  It will open the following dialog box, allowing you to specify an existing Microsoft SQL Server instance, method of connection, Report Server database name, and language.  You are also able to set the SharePointIntegrated property at the time of creation.  Supplied credentials will need the rights necessary to create a database on the SQL instance.  After configuration you may chose to connect to the databases in SQL Server Management Studio and change ownership if necessary.


Upgrade:  Clicking this button will automatically upgrade the tables in-place to the new schema for SQL 2005.  Perform this task if you are upgrading an existing instance of Reporting Services 2000 to Reporting Services 2005.  Make a point of backing up your databases prior to executing this command.  You can not roll back this action once completed.

Change:  Changing from Native to Sharepoint-Integrated mode for Reporting Services requires the creation of a new Reporting Services database.  Selecting this command will open the New Database dialog box.  The process from that point is identical to the creation of a new Reporting Services database.

You are able to script the changes made on this screen to be run at a later date by selecting the Script... button located at the bottom of the form.

create scripts

Sharepoint Integration

When running in Native mode, the following message will be displayed:


Configuring Reporting Services in Sharepoint Integrated mode will allow you to synchronize Reporting Services content with a Sharepoint site.  Setting up Sharepoint Integration is outside the scope of this tip.

Encryption Keys

encryption key

This form allows you to backup, restore, or make changes to the symmetric key that is used for encryption and decryption of data in this instance of Reporting Services.  The key is initially generated and activated upon creation of the ReportServer database.  Under certain circumstances, you'll need to make sure you have a backup copy of the key.  Such circumstances include:

  • Migration of a Reporting Services installation to a new server
  • Changing the service account associated with the Report Server Windows service
  • Configuration of a new report server in order to re-use an existing report server database previously established with another instance of Reporting Services

Restoration of an encryption key is required if you make Reporting Services service account changes without using the Reporting Services Configuration tool or if you're migrating Microsoft SQL Server Reporting Services to a new server.  According to Microsoft:  You should restore a symmetric key only if it is the same key that is currently used to encrypt and decrypt data in the report server database.  If you restore a symmetric key that is not valid, you will no longer be able to access sensitive data.  If this should occur you would need to delete the key and recreate it; both tasks would be accomplished via this form.  You will be prompted when deleting the symmetric key.  It is important that you are aware of the consequences before proceeding. 

configuration manager

The process of deleting a symmetric key is not reversible.  When you delete a key, you delete all data that is encrypted with the key.  This would include, but not be limited to, such valuable data as subscriptions, report data sources, and connection strings.  It is also important to note that only the Report Server Windows service account is able to unlock and use the key.  If you make changes to this service you'll be unable to use the key.

Email Settings

email settings

One of the most-important services provided by Reporting Services is the ability to schedule and deliver reports via email.  As is the case with Microsoft SQL Server 2005 Database Mail, this is accomplished via the Simple Mail Transport Protocol (SMTP).  In order to properly configure this component of Reporting Services, you'll need to supply a sender address, and the SMTP server/gateway to use.  Though a textbox is supplied for deliver method, the only method allowed in Reporting Services is SMTP.  The only requirements is that the sender email address has permissions to send email from the SMTP server you're specifying and that the SMTP server is a local server or SMTP server on your network.  The email address you supply will be in the "From" field of all outgoing email from this Reporting Services instance.

Execution Account

execution account

Setting up an Execution Account allows Reporting Services to operate under certain circumstances when credentials are not supplied.  Connecting to data sources that do not require authentication, such as XML for instance.  Best practices states that this account should be different from any of the service accounts set up previously for Reporting Services.  Any Windows account is acceptable for use, though the login should have sufficient rights to read locations holding the data or files you'll be accessing.  It will also need to have network login permissions.

At this point, if you've completed the forms in a manner that correctly conforms to your environment you should be ready to continue on with building and deploying reports to this instance of SQL Server Reporting Services.

Next Steps
  • Navigate to Report Manager and take a look around.
  • A higher-level overview of the Reporting Services Configuration Tool can be found here if you have lingering questions that not been answered in this tip.
  • Build and deploy a report via the Business Intelligence Development Studio (BIDS)
  • Review more Reporting Services Tips

sql server categories

sql server webinars

subscribe to mssqltips

sql server tutorials

sql server white papers

next tip

About the author
MSSQLTips author Tim Ford Tim Ford is a Senior Database Administrator with MindBody.

This author pledges the content of this article is based on professional experience and not AI generated.

View all my tips

Comments For This Article

Monday, December 15, 2014 - 11:55:29 AM - Dinesh DBA Back To Top (35610)

I had configure email s

When i click report => manage => New Subscription then it showing following error 


parameter validation failed .It is not posoble to provide valid valus for all paramater 

rsparamaeter error

Saturday, September 20, 2014 - 3:16:51 AM - PRABHAKAR PANDEY Back To Top (34637)


I am unable to access service broker url in my asp.net web apps it gives http401 unauthorized error...

pl suggest me..

Friday, September 19, 2014 - 6:25:25 AM - Dinesh Dba Back To Top (34619)


client:-       http://localhost/Reports_MSSSQLSERVER/Pages/Folder.aspx
Server:- http://localhost2/ReportServer

It is working for named instance but if is default instance then client url is not working..

Please suggest me solution.

Wednesday, September 17, 2014 - 6:48:24 AM - Dinesh Dba Back To Top (34559)

Hi ,

Unknown Host

Description: Unable to locate the server named "inmumnkpstw1020" --- the server does not have a DNS entry. Perhaps there is a misspelling in the server name, or the server no longer exists. Double-check the name and try again.

Please suggest me solution..


Dinesh DBA

Monday, April 28, 2014 - 10:50:49 AM - John Sikwese Back To Top (30533)



I have been bothered a lot during installation of Data Protection Manager 2012 r2,


I have installed SQL Sever 2008 R2


Now during installation of dPM 2012 R2,


I get this error:


Report Configuration failed.

Verify that SQL Server reporting Services is installed properly and that it is running.

ID: 812

Wednesday, December 18, 2013 - 11:53:11 AM - Lionel Back To Top (27832)


We have installed a primary and secondary SSR instance, on 2 servers located on 2 sites.

Encryption key has been backuped for each SSRS instance.

Primary and secondary SSRS instances are linked to the same SQL instance, containing ReportServer databases.

When we try to stop primary SSRS instance and to start secondary instance, it does not work.

If we try to restore key in secondary SSRS instance, we got following error :

Microsoft.ReportingServices.WmiProvider.WMIProviderException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

at Microsoft.ReportingServices.WmiProvider.RSWmiAdmin.BackupEncryptionKey(Byte[]& encryptedBytes, String password)

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.BackupEncryptionKey(Byte[]& encryptedBytes, String password)



Do you have an explanation to this problem ?


thanks you !




Monday, August 12, 2013 - 9:19:49 PM - ColmARocK Back To Top (26264)

Hello all, easy question for you. Could you give me the path where I can launch the Reporting Services Configuration Manager. Someone had delete the shortcut in the start menu.



Thursday, August 1, 2013 - 6:09:40 AM - Sunil Kumar Back To Top (26083)


Request you to help me in the below issue.

We have SSRS Reports working successfully in Development Environment with Network Service Account. For this, We have given restriction access to specific users for SSRS reports under Development Environment. Its restricting properly in Development Environment;

But in the Production Environments the SSRS Reports have set up with  Local Service Account. We have also given restriction to specific users for SSRS reports under Production Environment just like Development Environment. But, Its not restricting properly in Production Environment; Evey user is able to access the report even we have provided restricted to some users even though the reports are being viewed for that users.

We have tried to change from Local Service to Network Service in the Production Environment. When changing, its throwing an Encryption Exception.

Could you please help me regarding this and I would be thakful to you if you send me a mail to [email protected]





Friday, January 11, 2013 - 6:52:33 AM - zawzaw Back To Top (21398)

HI! I wanna know how to configure !!! There is an error message as below


System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
   at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
   at ReportServicesConfigUI.Panels.WindowsServiceIdentityPanel.StartWindowsServicePreChangeWindowsServiceIdentity(ServiceController rsService)

Thursday, January 10, 2013 - 11:50:34 PM - priyank jain Back To Top (21388)


Request you to please help me in below issue.

I am getting below error when i am trying to connect to reporting services through sql server management studio in sql server 2005.

ASP.Net 2.0 , IIS 6.0 is already installed on system. 


Error details  - 


Cannot connect to <hostname>.

Additional Information:

Unable to connect to the remote server (Microsoft.SqlServer.Management.UI.RSClient)

No connection could be made becuase the target machine actively refused it <some other ip address>:80 (System)





Wednesday, August 8, 2012 - 9:53:23 AM - rama Back To Top (18959)

I already have installed the full SQL Server 2008 R2 (SSMS,SSIS,SSRS,SSAS) on my machine before, today I installed (with out configuration) the SSMS & SSRS for 2008R2 on Administrator account with named instance. It was successfully installed. I can able to connect to the database through SSMS. But unable to do reporting services configuration connection, it showing "no report server found" error. Could you please help me.

Tuesday, July 3, 2012 - 11:44:46 AM - Teb Back To Top (18323)

I am trying to get connected to Sql server 2005 to set it up as a server for 2008 Reporting services. Unfortunately, i keep getting the error "A connection to the computer cananot be established. Details: Access is denied." I dont know why this is happening and was wondering if someone could point me in the right direction 

Monday, July 12, 2010 - 2:14:41 PM - JCoxJr Back To Top (5816)

I cannot seem to get Web Service Identity form to go Green

I cannot enter anything in the ASP .NET Service Account field

No matter what I enter in the other two fields, it gives me errors even though I have virtual names for both configured


can anyone assist ?

A virtual directory must first be created before performing this operation.

Note: it is already created

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)


Tuesday, December 22, 2009 - 3:51:56 PM - longinthetooth Back To Top (4600)

Hi there,

I have a customer with SSRS (SQL 2005 standard edition) installed on Windows 2003 server. The issue is that the Report Manager Virtual directory is greyed out and I cannot get to the setup of that virtual directory.

I did not do this setup as this client insist on doing it all themselves. What are the steps that I can take in order to correct this issue? Have you encountered this issue at clients?





Monday, July 13, 2009 - 8:37:05 AM - wadadlitech Back To Top (3727)

I followed the article but after going through all the options in the configuration tool, i am not seeing my reports manager page or server page. I get this error and i think it may have something to do with my Initialization tab not being checked but greyed. Any ideas? Everything else except SharePoint Integration and Encryption Keys are Configured. Should Initialization be greyed out? The server status does show Initialized and service status is running but i cant see my report manager page. The sql account does have admin rights...cant figure out why i am getting this message. Please help!

Server Error in '/ReportServerDev' Application.

The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.]
   System.Web.HttpRuntime.SetUpCodegenDirectory(CompilationSection compilationSection) +3591451
   System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags) +222

[HttpException (0x80004005): The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3540923
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +69
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +275

Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.8



Wednesday, June 4, 2008 - 7:46:33 PM - Wounded_Ego Back To Top (1087)

As far as I can tell, Vista won't run SSRS. I moved over to a Server 2008 machine and everything just flew together with no problems.

Thanks for your help.

 Now, I have to get past the "forcibly killed" connection for Management Studio...


Wednesday, June 4, 2008 - 6:40:04 PM - timmer26 Back To Top (1086)

That is an option worth trying.  Unfortunately I've not any experience with the combination of SQL version and O/S that you're dealing with.

Wednesday, June 4, 2008 - 5:33:06 PM - Wounded_Ego Back To Top (1085)

No improvement.

Might I need to manually create the virtual directories? Because I don't see them on my website.



Wednesday, June 4, 2008 - 4:33:01 PM - timmer26 Back To Top (1084)

SSRS 2008 on Vista huh?  Could not find a hammer to hit your thumb with or a stick to poke in your eye?  What I am getting at is that this is a painful combination.  I personally have little experience with it, but I can offer up a suggestion from what I've been told.  Let us all know how it works for you.

  1. Go to the RS Config tool
  2. Select Web Service Identity
  3. Set Report Server and Report Manager to Classic .net app pool

Alternately you could try going into IIS manager, click on the website, choose ADVANCED SETTINGS and change the Application Pool setting to Classic .net app pool.


Wednesday, June 4, 2008 - 3:41:31 PM - Wounded_Ego Back To Top (1083)

Also, I'm surprised not to see a /Reports or /ReportServer virtual directory listed on my Default Web Site. Is that normal?

Thanks again,

Wednesday, June 4, 2008 - 3:38:45 PM - Wounded_Ego Back To Top (1082)

I've spent days trying to get Reporting Services to work in my environment and hope you can help me...

 I have Sql Server 2008 Standard and Vista Ultimate.

 I have installed, and run through the Sql Server Reporting Configuration.

 When I navigate to http://localhost/Reports it automatically redirects me to: http://localhost/Reports/Pages/Folder.aspx  which is just a blank screen - Status is "Done"

If I navigate to http://localhost/ReportServer I get:

Server Error in '/ReportServer' Application.

Provider type not defined. (0x80090017)

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: Provider type not defined. (0x80090017)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[COMException (0x80090017): Provider type not defined. (0x80090017)]
   System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0
   System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +43
   System.Reflection.Assembly.InternalGetSatelliteAssembly(CultureInfo culture, Version version, Boolean throwOnFileNotFound) +211
   System.Resources.ResourceManager.GetSatelliteAssembly(CultureInfo lookForCulture) +79
   System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents) +297
   System.Resources.ResourceManager.GetString(String name, CultureInfo culture) +74
   Microsoft.ReportingServices.Diagnostics.Utilities.Keys.GetString(String key) +21
   Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException..ctor(Exception innerException, String additionalTraceMessage) +21
   Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.WriteErrorResponse(Int32 code, String shortHttpDescription, Exception exception, Boolean errorResponseAsXml) +67
   Microsoft.ReportingServices.WebServer.Global.WriteServerError(Exception e) +44
   Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e) +180
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

Version Information: Microsoft .NET Framework Version:2.0.50727.3031; ASP.NET Version:2.0.50727.3031

 Any ideas?


Friday, May 9, 2008 - 5:02:21 PM - timmer26 Back To Top (969)

This will occur if you're launching the Reporting Services Configuration Tool from a server/workstation that does not have Reporting Services installed on it.  When you close out of that message you'll be met by a different dialog box that will allow you to select the instance of Reporting Services you wish to connect to.  Enter the Machine Name where prompted, click the Find button and it will return a list of all instances on that server for SSRS.  Select the instance (the default is MSSQLSERVER) and click Connect.

Wednesday, May 7, 2008 - 3:34:51 AM - Arijit Manna Back To Top (951)



i have gone through the article posted on your website

SQL Server Reporting Services Configuration Tool

Written By: Tim Ford -- 3/12/2008

however i have a problem

when i open the launch the tool i get a message like this



 how to install/run Report Servers on my server ?

how do i access my database i want to work with ?

please help me immediately





get free sql tips
agree to terms