Deploying Report application question

I've finally got a report project (2005) finished and I'd like to 'deploy'
it
I've set up a website on a network server (with IIS running). Then, I set up
the targetSiteURL to that url - but I get the dreaded error message:
"A connection could not be made to the report server...(url)"
Maybe I misunderstood - I thought I was deploying the project as a web app,
so all I'd need was a working website directory.
What am I missing?You've missed a critical part. You are deploying to Reporting Services.
Reporting Services is a asp.net application. You do need IIS but when you
install reporting services it will create the two websites it uses. When you
deploy your report VS uses webservices to send the report, the data sources,
etc to reporting services. It then stored the report definition in the
database. No rdl exists as a file on the server.
Reporting Services also ships with a portal called Report Manager that is
used for managing roles and other admin tasks as well as providing a portal
for users (if you want to use it, that is all I use but some people create
their own web front end).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Elmo Watson" <sm@.here.com> wrote in message
news:%23TJgNJiUIHA.4880@.TK2MSFTNGP03.phx.gbl...
> I've finally got a report project (2005) finished and I'd like to 'deploy'
> it
> I've set up a website on a network server (with IIS running). Then, I set
> up the targetSiteURL to that url - but I get the dreaded error message:
> "A connection could not be made to the report server...(url)"
> Maybe I misunderstood - I thought I was deploying the project as a web
> app, so all I'd need was a working website directory.
> What am I missing?
>
>|||Thanks - next question is, how do I install Reporting Services on the other
server, so that it will create the two websites?
Can I do it remotely, through Business Management Studio, or does it need to
be done with a CD on that server?
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23JJArQiUIHA.1164@.TK2MSFTNGP02.phx.gbl...
> You've missed a critical part. You are deploying to Reporting Services.
> Reporting Services is a asp.net application. You do need IIS but when you
> install reporting services it will create the two websites it uses. When
> you deploy your report VS uses webservices to send the report, the data
> sources, etc to reporting services. It then stored the report definition
> in the database. No rdl exists as a file on the server.
> Reporting Services also ships with a portal called Report Manager that is
> used for managing roles and other admin tasks as well as providing a
> portal for users (if you want to use it, that is all I use but some people
> create their own web front end).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Elmo Watson" <sm@.here.com> wrote in message
> news:%23TJgNJiUIHA.4880@.TK2MSFTNGP03.phx.gbl...
>> I've finally got a report project (2005) finished and I'd like to
>> 'deploy' it
>> I've set up a website on a network server (with IIS running). Then, I set
>> up the targetSiteURL to that url - but I get the dreaded error message:
>> "A connection could not be made to the report server...(url)"
>> Maybe I misunderstood - I thought I was deploying the project as a web
>> app, so all I'd need was a working website directory.
>> What am I missing?
>>
>|||Business Management Studio is just for the development of the reports. As
you have seen you can develop reports without the server.
You need to get the media for SQL 2005 and install Reporting Services from
that. Besides IIS it also needs a database server somewhere. It creates two
databases that it uses for its metadata/object caching. The databases can
either be on the same box or a different box. Also, the DB can be either
2000 or 2005 for Reporting Services 2005. However, when installing RS 2005
you need a license for SQL 2005 even if you use SQL 2000 as your data store.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Elmo Watson" <sm@.here.com> wrote in message
news:u7MvKciUIHA.5264@.TK2MSFTNGP02.phx.gbl...
> Thanks - next question is, how do I install Reporting Services on the
> other server, so that it will create the two websites?
> Can I do it remotely, through Business Management Studio, or does it need
> to be done with a CD on that server?
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%23JJArQiUIHA.1164@.TK2MSFTNGP02.phx.gbl...
>> You've missed a critical part. You are deploying to Reporting Services.
>> Reporting Services is a asp.net application. You do need IIS but when you
>> install reporting services it will create the two websites it uses. When
>> you deploy your report VS uses webservices to send the report, the data
>> sources, etc to reporting services. It then stored the report definition
>> in the database. No rdl exists as a file on the server.
>> Reporting Services also ships with a portal called Report Manager that is
>> used for managing roles and other admin tasks as well as providing a
>> portal for users (if you want to use it, that is all I use but some
>> people create their own web front end).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Elmo Watson" <sm@.here.com> wrote in message
>> news:%23TJgNJiUIHA.4880@.TK2MSFTNGP03.phx.gbl...
>> I've finally got a report project (2005) finished and I'd like to
>> 'deploy' it
>> I've set up a website on a network server (with IIS running). Then, I
>> set up the targetSiteURL to that url - but I get the dreaded error
>> message:
>> "A connection could not be made to the report server...(url)"
>> Maybe I misunderstood - I thought I was deploying the project as a web
>> app, so all I'd need was a working website directory.
>> What am I missing?
>>
>>
>