You encounter report server connection failure with below error message. Below is one of the instance which I witnessed while connecting through SSMS, it fails while using the server name (SERVERNAMEABC)


You encounter report server connection failure with below error message. Below is one of the instance which I witnessed while connecting through SSMS, it fails while using the server name (SERVERNAMEABC)


Error:
=====


TITLE: Connect to Server
——————————


Cannot connect to SERVERNAMEABC.


——————————


ADDITIONAL INFORMATION:


The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version. (Microsoft.SqlServer.Management.UI.RSClient)


——————————


The request failed with HTTP status 404: Not Found. (Microsoft.SqlServer.Management.UI.RSClient)


——————————


BUTTONS:


OK


——————————


 


The above error message is self-explanatory and suggests that there is some issues connecting to report server. Error 404 is a very generic error message.


Below is what I tried in my environment to help resolve the issue.


 


1)       Try to connect to SQL Server reporting service in SQL Server management studio using http://localhost/reportserver  or http://servername/reportserver


2)       Check if this is successful.


3)       If connection to SSRS is successful with http://localhost/reportserver  and fails with <server name>


4)       Modify the rsreportserver.config as below.


<URL ROOT>http://SERVERNAMEABC/reportserver <URL ROOT>


 


Make sure you are able to use the above link in IE to connect to reporting service successfully.


After this you should be able to use the <server name> to connect to SSRS in SQL Server management studio


 


By,
Nikesh Mhatre
SE, Microsoft SQL Server


Reviewed by,
Nickson Dicson
Tech lead, Microsoft SQL Server


Comments (2)

  1. Bot says:

    How about if both using http://localhost/reportserver  or http://servername/reportserver is successfully working?

  2. Keith Montz says:

    Nikesh,

    Your step 4 is not helpful because it does not indicate where to add or edit this in the XML Configuration document. There is an entry with the <url root> in configuration but that doesn't mean that is the edit location. Think about it.  If I told you to add an entry into an XML configuration document, you would ask me where.

    It appears that Nickson Dicson rubber stamped it okay where then I ask where is the good quality control. Notice there is not the correct closing </URL Root> as you both missed the "/".  

    Regards,

    Keith