403 Forbidden in Reporting Services

I just spent a good chunk of time fighting a problem with my SQL Server 2005 Reporting Services installation. I had not previously used it on this machine so it should've been exactly as the SQL Server (and SP2) installation program configured it.

I started by deploying a new set of reports from Visual Studio over to the server, which worked straight away. I then went to the Web-based Report manager and could see my reports deployed, but as soon as I tried actually rendering one of the reports, I'd get an error like this one:

Remote server returned an error: (403) Forbidden

Long story short, the problem was in how the /Reports application references the services in the /ReportServer application, and I fixed it by going to IIS and modifying the /ReportServer application configuration to add "ReportService2005.asmx" as a possible default content page under the "Documents" tab of the application's property page.

Comments (5)

QuanJune 26th, 2008 at 11:53 am

Thanks, I spent considerable time on this.
One of my servers work without requiring this addition, but another won’t work until I added this. Not sure why, and not sure of the implications, but for now it’s working for me.

Greg MartinJuly 13th, 2009 at 9:33 pm

Thanks for posting this. Saved me hours…

\\Greg

Ramone HamiltonOctober 4th, 2009 at 11:54 am

Thanks for this, this had been a big problem for me.

Steve CallanNovember 16th, 2009 at 10:12 pm

Totally amazing fix that belies belief, but nonetheless, it solved the 403 error I was receiving on the second run of replicating an ASP/SSRS application. The first run worked fine without the addition of this file, the second would not render a report because of this error. Adding this file into the Documents section did the trick.

AshMarch 16th, 2010 at 6:33 am

Weird, I have no idea why this resolved my issues, RS was working fine 1 day then next not and only this fixed it

Leave a comment

Your comment