hi i just made a new install of sql server 2008 r2 with reporting services. unfortunately i'm not able to access the two urls. i get an 404. does anybody know that problem? i switched off uac, started ie as admin, added the sites to the trusted sites, opened port 80, changed the port in rss to 8080.... no positive solution. thanks for your help

no idea? it's quite urgent.... thanks!

have your configured SRS after the installation? here is a good write up on setting up SRS for ConfigMgr. http://blogs.technet.com/b/mwiles/archive/2009/02/19/east-setup-of-srs-with-config-manager-r2.aspx Thanks, Brandon

hi brandon yes. thanks for the link, but it's not 2008 r2.

CRMBE the instructions are virtually the same for 2005 and 2008. Are you trying to access the report URLS from an account that is a local administrator on the box that it was setup on? If not then you just dont have permissions to view the webpage. try logging on from the server with a local admin account going to the URL's and setting the appropriate permissions provided that you have already configured SRS.

the user is local admin and the db owner

on the server check the SRS logfiles to see what is causing the problem. post any errors. Logs can be found in the below location or simliar to where you installed to. C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles

Ok. One is: "Failed to get report server reservations" or another "No URLs specifed for Application ReportServerWebService. It will be ignored" Or: "Cannot find secure url from reservations." Or: "Für den Vorgang, den Sie ausführen möchten, ist eine sichere Verbindung (HTTPS) erforderlich."

I just found out, that the urls with https work, but with http not.... http://servname:80/reports (error) or https://servername.domain.topleveldomain:443/reports (works) http://servname:80/reportserver (error) or https://servername.domain.topleveldomain:443/reportserver (works)

Glad i could help! If you are fine with that you can leave it as is or you can open Reporting Services Configuration Manager and change the URL's to use HTTP instead.

Thanks Brandon, but why aren't both working? In earlier versions the http-version worked without making anything. I'd like http, but in the Config Manager I can't set wheter to use http or https. There are just both URLs displayed. I just deleted the https binding for test purposes. http still not working...

CRMBE this is now handled in SRS and has to be configured in Reporting Services Configuration Manager not in ConfigMgr. SRS can be set with a SSL identity so you can have both but requires a certificate for the SSL to be configured.

Yes, I am in the RSCM and the https is working fine with the SSL certificate. But now I'd also like the http to get working...

once you are in RSCM go to the web service url and report manager URL's and select the advanced tab enter a custom port and select ok you should now be able to access from the custom port i.e. port 80 if you want http. http://technet.microsoft.com/en-us/library/bb630447.aspx

I've already tried that, but that doesn't work. A cert error appears and then the 404 error...

Do you have a ceritificate listed that is valid? I would suggest to revert everything back to port 80 verify that all is working fine then try and add 443 as a binding back with a proper certificate and see if that works...

It's just the standard server cert. I don't have a "real" one. The http-URL is port 80 and I also played a little with this port - no chance! I still get the following errors: Failed to get report server reservations" or another "No URLs specifed for Application ReportServerWebService. It will be ignored" Or: "Cannot find secure url from reservations." Or: "Für den Vorgang, den Sie ausführen möchten, ist eine sichere Verbindung (HTTPS) erforderlich."

Hi. I was able to solve my issue of the Report Manager URL not working when using HTTP, but working using HTTPS. A netmon trace revealed that an HTTP 302 redirect request to the HTTPS page. I modified the rsreportserver.config file to update this line: <Add Key="SecureConnectionLevel" Value="0"/> The original value was set to 2. Here is a great post on the different values and a better explanation of the underlying issue: http://blog.hoegaerden.be/2009/05/24/reporting-services-2008-and-ssl/Jason Ogle MCITP Enterprise Administrator