I ran into this issue and was happy to find this solution. Thought of sharing this fix and also for my future reference purpose.



Error: The attempt to connect to the report server failed. Check your connection information and that the reportserver is a compatible version. The request failed with HTTP status 404: Not Found.



This means that you have configured the /reportserver/ app to not be reachable via
http://localhost/...



Solution:



a) Add the localhost hostheader to the web-site which hosts the /reportserver/ and make sure the app is then reachable via that path.



b) Edit the file -

C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\ReportManager\RSWebApplication.config



and add the full url to the ReportServer into the ReportServerUrl tag (no ending / nessesary) AND remove the value from ReportServerVirtualDirectory (otherwise you get nasty, unprecise exceptions). THEN you must recycle the app-pool used by the Report-Manager so that config file is being reloaded



<UI>

<ReportServerUrl>http://localhost/reportserver
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>

<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>

</UI>



Reference: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=198252&SiteID=1

6 comments

  1. Anonymous // December 22, 2010 at 2:01 AM  

    I also face same issue as "The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version."

    Resloution - In code, while assigning report viewer property ReportURL we gave http:\\servername\reports path instead of http:\\server\reportserver path.

    If you are making the same mistake then replace URL to \reportserver. This will reslove the issue.

  2. Anonymous // July 3, 2012 at 7:13 AM  

    We found that when copying in a string from Word to notepad in the web.config file, the quotes held as smart quotes (thicker quote font type) and caused this error. When typing in the quotes in notepad in the web.config it was fine.

  3. Anonymous // July 29, 2014 at 4:09 PM  

    Also I have noticed that, unfortunately while editing the web.config file I placed the end string "/>" twice and this caused the same issue. It took me a while to figure out.

  4. joy // January 8, 2015 at 12:33 AM  

    I accidentally viewed your blog and I was so amazed with your work that it touched the deepness of my heart. It made me sentimental. Thanks for posting.

    n8fan.net

    www.n8fan.net

  5. Leslie Lim // October 2, 2015 at 7:45 PM  


    I have found your blogs to be friendly and welcoming. Thanks for making this one. I really enjoy reading and surfing it. Try to visit my site @ www.imarksweb.org

    Zean

  6. Keyur Patel // March 1, 2016 at 6:02 AM  

    Hi Techie Cocktail,

    The same issue is with me.

    Logged case with Microsoft SQL Server team. But also the are not able to resolve this.

    I tried with the same settings as you suggested on your post but it unsuccessful at my end.

    Can you suggest me other alternative if any?

    Do email me knp8swa@yahoo.co.in or knp8swa@yahoo.co.in

    I'm stuck with the error since last 10 days. Any help will be really appreciable.

    Thanks ad Regards,
    Keyur Patel