Reportserver deploy other then Localhost

Hi I'm very new in this area so please be patience...
We run windows server 2003 and SQL 2005 and Reportservices.
We have build several reports which we can see on
http://localhost/Reports/Pages/Folder.aspx
However if we deploy these report to a webpage using the option inVisual
Studio,
Project/"project name/Properties then we get and error.
"connection couldn't be established Url//name.
If we try to add teh following link on the page of our websit we get the
message.
"this page couldn't be found"
What kind of setting/option/path should we follow to get this established?On Jul 4, 3:14 am, SQL-Herbie <SQLHer...@.discussions.microsoft.com>
wrote:
> Hi I'm very new in this area so please be patience...
> We run windows server 2003 and SQL 2005 and Reportservices.
> We have build several reports which we can see onhttp://localhost/Reports/Pages/Folder.aspx
> However if we deploy these report to a webpage using the option inVisual
> Studio,
> Project/"project name/Properties then we get and error.
> "connection couldn't be established Url//name.
> If we try to add teh following link on the page of our websit we get the
> message.
> "this page couldn't be found"
> What kind of setting/option/path should we follow to get this established?
Traditionally, I like to deploy reports to other servers via the
Report Manager on the other server. All you would need to do is upload
the RDL file and set the datasource to an available datsource in the
Report Manager (if one exists already; otherwise, create one). Hope
this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||"EMartinez" wrote:
> On Jul 4, 3:14 am, SQL-Herbie <SQLHer...@.discussions.microsoft.com>
> wrote:
> > Hi I'm very new in this area so please be patience...
> > We run windows server 2003 and SQL 2005 and Reportservices.
> >
> > We have build several reports which we can see onhttp://localhost/Reports/Pages/Folder.aspx
> >
> > However if we deploy these report to a webpage using the option inVisual
> > Studio,
> > Project/"project name/Properties then we get and error.
> > "connection couldn't be established Url//name.
> >
> > If we try to add teh following link on the page of our websit we get the
> > message.
> > "this page couldn't be found"
> >
> > What kind of setting/option/path should we follow to get this established?
>
> Traditionally, I like to deploy reports to other servers via the
> Report Manager on the other server. All you would need to do is upload
> the RDL file and set the datasource to an available datsource in the
> Report Manager (if one exists already; otherwise, create one). Hope
> this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>
Sorry but what kind of tool(s) should we use to read these RDL files
Secondly we loose the functionality of the reportserver...|||On Jul 5, 1:14 am, SQL-Herbie <SQLHer...@.discussions.microsoft.com>
wrote:
> "EMartinez" wrote:
> > On Jul 4, 3:14 am, SQL-Herbie <SQLHer...@.discussions.microsoft.com>
> > wrote:
> > > Hi I'm very new in this area so please be patience...
> > > We run windows server 2003 and SQL 2005 and Reportservices.
> > > We have build several reports which we can see onhttp://localhost/Reports/Pages/Folder.aspx
> > > However if we deploy these report to a webpage using the option inVisual
> > > Studio,
> > > Project/"project name/Properties then we get and error.
> > > "connection couldn't be established Url//name.
> > > If we try to add teh following link on the page of our websit we get the
> > > message.
> > > "this page couldn't be found"
> > > What kind of setting/option/path should we follow to get this established?
> > Traditionally, I like to deploy reports to other servers via the
> > Report Manager on the other server. All you would need to do is upload
> > the RDL file and set the datasource to an available datsource in the
> > Report Manager (if one exists already; otherwise, create one). Hope
> > this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
> Sorry but what kind of tool(s) should we use to read these RDL files
> Secondly we loose the functionality of the reportserver...
To read the RDL file itself (non report view of course) you could use
a standard text editor (Notepad, Wordpad, Notepad++, etc). If you are
saying that you do not have SSRS/Reporting Services installed on the
machine you are deploying them to, you may run into the issue where
the reports cannot be viewed, since it requires the RS service to be
running on the machine that is hosting the reports (so to speak).
Also, you might want to look into the RS.exe utility for the command
line. Hope this helps further.
Regards,
Enrique Martinez
Sr. Software Consultant|||I think there is some communication problem going on in this thread.
The ability to deploy the report from VS is how you get a report into
Reporting Services. If you can see the reports on your server (which the
below seems to be the case) then you have already deployed the report.
What are you trying to do when you use the phrase "deploy these report to a
webpage". Are you trying to deploy to another reporting services server? Or
are you trying to view the report in your own webpage somewhere else.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"SQL-Herbie" <SQLHerbie@.discussions.microsoft.com> wrote in message
news:5FB85260-24A8-4D96-8E1A-FC9E9CEE281C@.microsoft.com...
> Hi I'm very new in this area so please be patience...
> We run windows server 2003 and SQL 2005 and Reportservices.
> We have build several reports which we can see on
> http://localhost/Reports/Pages/Folder.aspx
> However if we deploy these report to a webpage using the option inVisual
> Studio,
> Project/"project name/Properties then we get and error.
> "connection couldn't be established Url//name.
> If we try to add teh following link on the page of our websit we get the
> message.
> "this page couldn't be found"
> What kind of setting/option/path should we follow to get this established?
>