Error 401 accessing the Report Manager in an environment configured in Scale Out

When using a load balancer with several nodes in Reporting Services, you might notice that the Report Server (http://<machinename>/Reportserver)
is accessible but Report Manager (http://<machinename>/Reports) produces the following error:


The request failed with HTTP status 401: Unauthorized.


1. First of all you need to make sure that you configured the scale out of Reporting Services correctly by following the indications from the article below:

 Configuring a Report Server Scale-Out Deployment


2. After that, if you have problems accessing the Report Manager locally, you can try disabling the loopbackcheck (steps in the link:


3. If you still have problems accessing the Report Manager remotely try modifying the <ReportServerUrl> in the RSReportServer.config file with the url of the reportserver of the node.


The URL of the report server site for which the Report Manager tool searches is specified in the ReportServerUrl tag in the file RSWebApplication.config file. By default, if you leave this tag blank, the Report Manager tool uses "Localhost" as the server URL.




Maria Esteban

Reporting Services Support Engineer

Comments (1)

  1. pregunton says:

    I use ReportService


    I use powershell script por deploy RDL files in SSRS 2008 server

    and I get error

    Message: Exception calling "DeleteItem" with "1" argument(s): "The request failed with HTTP status 401: Unauthorized."

    With the same credential, in IE is ok http://DEVRPS/ReportServer/ReportService2005.asmx?WSDL

    In Report Services 2008 by default it uses its own built-in server, not IIS. You'll need to check in the reporting services directory on your server (its in the usual MSSQL directory in Program Files) to see the configuration files and make changes (you can also make some through reporting services configuration manager). Microsoft does not recommend installing IIS on the reporting services server.

    SSRS 2008 doesn't use IIS

    troubleshoot IIS and 401 not useful then for me…/907273

    Any suggestions ?

Skip to main content