I have installed SQL SERVER Katmai with default settings but for some reason I cannot access the Reporting Services. When I go to the Reporting Services Configuration I cannot configure the WebService URL. I also cannot accesshttp://<servername>/Reports orhttp://<servername>/ReportServer. Can someone tell me what the problem could be?
Service is running, however, I cannot get into the ReportServer through the SQL Server Management Studio or Internet Explorer. All other services are operating fine. I even checked to make sure there were no IIS sites with the same name as Reports or ReportServer.
Reporting services is behaving different, in the SQL Server Configuration manager the "log on" properties tab for the "Reporting Services" says that Account settings &c are managed by the Reporting Services Configuration tool and it shows a disabled button labeled "Not Installed".
In the Surface Area Configuration tool I get an "invalid namespace" error on all 3 Reporting services items, 2x for system.management and once for sqlsac.
And the Reporting Services Configuration tool freezes when I click the WebService URL option. The Report Manager URL does work, and so does the link to the web interface, using port 8080. Trying to add or edit the entries in the "multiple identities" list under the "advanced" tab however also results in the tool freezing.
And this is using XP Pro SP2.
I am on Windows XP Pro with SP2 and I don't have any issues. You can use the Web Service URL link in the RS Configuration utility to change the port. Assuming you are running on port 8080, http://localhost:8080/reportserver should respond.
I am using Vista Home Premium and the Reporting Services does not work even though the others services do. My next step is to upgrade to Vista Ultimate and put Kamai on my Windows 2003 Server. I understand that there are processing that don't work on the Home editions of Vista that work on the Business editions. I will report my findings.
Vista is not officially supported with the July CTP. For better experience I'd recommend you stick with Windows XP .
That is right, I had already seen that http://localhost:8080/reportserver did work. But I had to dig into some .config files to find that URL, as it didn't work via the Reporting Services Configuration tool. So, I still wonder what's causing the problems I described...
Is therer something else listening on the original port (probably 80)? What does netstat -no show?
Sure, the standard IIS webservice. Has to be there for the installation to run smoothly.It choked a few times when I had an Apache server active there. But that's all OK now. It's not the web interface that has problems. It's SAC and Reporting Services Config.
