403 Forbidden in Reporting Services

Link. June 11, 2008. Comments [1]. Posted in:

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.



Thursday, June 26, 2008 1:53:52 PM (SA Pacific Standard Time, UTC-05:00)
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.
Quan
Comments are closed.

Syndicate

About

Tomas Restrepo is a software developer located in Colombia, South America. His interests include .NET, Connected Systems, PowerShell and lately dynamic programming languages. More...

tomasrestrepo @ twitter My Flickr photostream My saved links on delicious My Technorati Profile

email: tomas@winterdom.com
msn: tomasr@passport.com

View my profile on LinkedIn

MVP logo

Ads


Categories

Statistics

Total Posts: 1050
This Year: 1
This Month: 1
This Week: 0
Comments: 825

Archive

Other

Copyright © 2002-2008, Tomas Restrepo.

Powered by: newtelligence dasBlog 2.2.8279.16125

Sign In