Go it IIS and righ click and browse the ReportServer virtual directroy. if
you can see the report then the ReportServer is working otherwise there is
some problem in ReportServer. Then you have to lookinto the log for the issue.
You are correct, when SQL Server 2005 got installed it did not create the
ReportServer or Report Web sites under the Default IIS web site. My next 2
questions are why didn't these get created by default when installing the SQL
Server 2005 installation and is there an install script to do this after the
fact that SQL Server 2005 is already installed?
Thanks,
Eve
> Go it IIS and righ click and browse the ReportServer virtual directroy. if
> you can see the report then the ReportServer is working otherwise there is
[quoted text clipped - 21 lines]
> > > > Thanks,
> > > > ESDba
Bruce L-C [MVP] - 30 Aug 2006 19:10 GMT
Check and see if you have any databases for RS either (it creates two). If
not, then you did not get any of RS installed.

Signature
Bruce Loehle-Conger
MVP SQL Server Reporting Services
> You are correct, when SQL Server 2005 got installed it did not create the
> ReportServer or Report Web sites under the Default IIS web site. My next
[quoted text clipped - 43 lines]
>> > > > Thanks,
>> > > > ESDba
Bava Mani - 30 Aug 2006 19:40 GMT
If you have installed Reporing Service 2005 check if the ReportServer
database is availble. If its avilable then use the Report Server Configuarion
Manager Tool available under SQL-Server2005 program shortcut. It provides
option to create virtual directory,change report settings, etc.. Then Open
Report Manager to test if the ReportServer is working fine.
> You are correct, when SQL Server 2005 got installed it did not create the
> ReportServer or Report Web sites under the Default IIS web site. My next 2
[quoted text clipped - 30 lines]
> > > > > Thanks,
> > > > > ESDba
ESDba - 30 Aug 2006 20:31 GMT
I am making serious progress, I went into IIS and the ReportServer and Report
Web sites were not created under the default web site, so this indicated that
Reporting Services did not install properly during the installation. I reran
the
setup for SQL Server 2005 and went into "advanced tab" and selected to just
re-install Reporting services all components. After this, I went into the
Reporting Services Configuration tool and it could not connect to Database,
and had to go into the SQL Server Configuration Manager and reset all the
domain logins and start all appropriate services. Then I went through each
option in the Reporting Services Configuration Tool and all components got
re-installed except the Connection to the ReportServer database. I manually
created this database outside of this utility and tried to connect, but it
was looking for Service Pack 1. I am now installing this and hopefully this
last step will allow me to connect to the ReportServer database for Reporting
Services reports. I still need to change the properties on the TargetServer
URL in the properties right when this is all over and try to Deploy?
Hopefully this is the last step to get set up. Why didn't all these pieces
get set up when I originally ran the entire SQL Server 2005 setup? I did
check off Reporting Services?
Thanks a million,
ESDba
> If you have installed Reporing Service 2005 check if the ReportServer
> database is availble. If its avilable then use the Report Server Configuarion
[quoted text clipped - 36 lines]
> > > > > > Thanks,
> > > > > > ESDba
Bava Mani - 30 Aug 2006 20:44 GMT
Ya during intallation of reporting service in 2005. it will ask whether it
will create the default website\VirtualDirectory for Reports and
ReportigService or do you want to create later. you should have choosen to
create later. If you change your Execution account detail after installtion
then you will not able to access ReportServer database.. i think thats what
happened in your case..
> I am making serious progress, I went into IIS and the ReportServer and Report
> Web sites were not created under the default web site, so this indicated that
[quoted text clipped - 59 lines]
> > > > > > > Thanks,
> > > > > > > ESDba