Sql Server Reporting Services 2005 returns 404 not found

RobFarmer


I just installed Sql Server Reporting Services 2005 on a Windows Server 2003 R2 x64 server. I configured Reporting Services through the Reporting Services Configuration tool and everything has a green checkmark.

I'm trying to connect to the webservice, but keep getting 404 not found errors. I've tried putting the following into a web browser and all return a 404 error:

http://msql01/reports/
http://msql01/reportserver/
http://msql01/reportserver/reportservice.asmx wsdl
http://msql01/reportserver/reportservice2005.asmx wsdl

I've tried edting the RSWebApplication.config file using the following configurations (restarting IIS afterwards) without any luck:
<UI>
<ReportServerUrl></ReportServerUrl>
<ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>

and

<UI>
<ReportServerUrl>http://msql01/ReportServer/</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>

Any help is appreciated!

Thanks,
Rob

Bret Updegraff

Rob,

Do you have SQL Installed as the default instance or a named instance

Also, is anything logged in RS or Event Viewer that may lead to the problem

-Bret

RobFarmer

Its installed as the default instance.

I've checked the event log and the reporting services .log files and can't see any errors.

Rob

Bret Updegraff

It sounds like IIS/Security may be locked down on this server. Have you checked the file permissions to the report manager files

C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\ReportManager

Can you access a web page from the default web c:\inetpub\wwwroot

try adding a simple .htm page and pulling it up thru a browser.

Is home.aspx set as the default document under the Reports virtual directory properties

RobFarmer

File permissions look correct to me. From IIS the virtual directory has read access (I also added Script Source and Write to be sure). The files themselves have read/write permissions for two reporting services users, and SYSTEM, Administrators, AND Users group all have full control.

I added a test htm page it it loaded.

Home.aspx is set as the default document under the Reports virtual directory and I tried explicitly entering home.aspx into the URL.

ggable

I am having the same problem, however it is not a new install - it had been runnning for a couple of months. As far as I know, nothing in the application or IIS settings were changed by a person.

Configuration GUI has all green check marks. I stopped/started the service and I stopped/started the IIS website. I rebooted the server.

I checked the file permissions in IIS - they appear to be unchanged (read access).

I have looked at the eventvwr and the reporting services logs. I dont see anything out of the ordinary. I do, however, see an entry 4 days ago that indicates "Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database." I do not see another entry after that one.

I verified that home.aspx is the default document. I also tried typing it into the url, without success. I also added a test page and it loads fine.

What are the next places to check

Is there a log or some other way of confirming that if IIS settings and/or SSRS settings were changed, what and who

Thanks!

- Glenda

RobFarmer

Glenda-

I had the same "Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database." in the event viewer, but figured it was due to a new install and before it was configured.

Still no luck...

Rob

ggable

I did a little more digging and found out the substatus code in the IIS logs was 2 (therefore 404 2) which is "Not Found - Denied due to Lockdown Policy"

I dont know exactly what this means yet, although the microsoft definition is:

If a request is denied because the associated ISAPI or CGI has not been unlocked, a 404.2 error is returned.

I am going to do more digging and will post what I find.

- Glenda

ggable

ok... I found it!

In IIS - verify that under web service extensions - ASP.NET 2.0 is allowed (not prohibited). If it is not listed at all, it needs to be added and then allowed.

If this does not solve your problem, look at the IIS logs (properties for the main website and click on properties of the logging to find out where the logs are being stored) - what is the number after the 404 error code for the appropriate GET My IIS Administration book might be able to help a little

RobFarmer

AWESOME! That did it!

I had this same issue with my web server, can't beleive that was it again. Thanks so much Glenda!

Rob