by Rick Glos
24. July 2008 19:44
I finally have need to do some development against SQL Server Reporting Services (SSRS). Unfortunately the first time I tried to browse to http://localhost/reports I get this nice error: Unable to connect to the remote server.
I'm not sure why it got to this state. I installed SQL Server with the defaults, including SSRS. It should've been up and running. But if anything, I've learned Vista has introduced alot of peculiarities. So here's how I fixed it in case someone else finds this useful.
Here's the screen you'll get when you try and use Report Manager:
I guess the problem revolves around IIS 7. So we need to crack open IIS 7.0 and then navigate down to the ReportServer virtual directory. Make sure you are in Content View mode (which you can switch from the two tabs on the bottom row or via a right-click). Double click on Handler Mappings.
You should see that ISAPI is disabled.
Here's how we enable it. Click Edit Feature Permissions in the toolbar to the right:
In the pop-up windows we need to check the Script and Execute:
ISAPI will now be enabled:
Now you'll correctly see the SSRS web interface.
And you can see that in the screenshot above, I'm not seeing any folders or command options. Even though my account was in the local administrators group, I still had to add account as Content Manager by launching IE as admin. Additionally, I also had to add localhost to the Trusted Sites collection. Once that was done, I was able to see objects and commands...
This was alot more complex than I expected. How does Microsoft expect casual users to configure this stuff?
Anyway, later.
91b4f9b4-c9c2-4429-b649-0e37a7372a2c|3|5.0
Tags: programming
Subscribe