"Unable to Connect" Report Manager - IE

[swhitten]

I installed the following on my Windows Vista Ultimate laptop:
IIS
SQL 2005 with reporting services
SQL 2005 SP3

I did a named instance of SQL. Phoenix is the machine name. SQL1 is the SQL instance name.

When I open Internet Explorer and try to go to

http://phoenix/reports$sql1,

it looks like it is trying to connect, then it gives me this error:

Error
Unable to connect to the remote server.

It did not ask me for a user name and password.


If I try to go to

http://phoenix/reportserver$sql1,

I get:

The website declined to show this page.
This website requires you to log in.
This error (HTTP 403 Forbidden) means that IE was able to connect to the website, but it does not have permissions to view the webpage.

During the SQL 2005 installation, all prerequisites in the System Configuration Check, including IIS, had green checkmarks - acceptable, so I think my IIS is okay.

If I open Reporting Services Configuration Manager, I have green checks for everything down through Database Setup. Sharepoint Integration and Encryption keys have blue question marks. Initialization has a greyed out check. Email Settings and Execution Account have yellow exclamation marks.

I am trying to get SRS up and running for a class I am taking later this month. I am a complete novice when it comes to SRS and IIS.

Any help you can offer will be appreciated.

 

[ks2000]

Have you verified your credentials to that Report Server?


Thanks

 

[bburnell]

Did you try adding in the port, like this?

http://phoenix:8081/Reports/Pages/Folder.aspx

--------------------------
Web/.net Programmer & DBA
Central PA

 

[swhitten]

I don't understand this enough to really explain it, but it had to do with some configuration in Reporting Services Configuration and IIS Manager - all because of named instance of SQL and Vista.

We changed the name of the report server and report manager in Reporting Services Configuration to be just "ReportServer" and "Reports" without reference to the sql instance at the end.

We changed the defaultapppool in IIS Manager to be Classic instead of Integrated managed pipeline mode.

Thanks for your help!