Issue with ReportViewer dll and accessing reports

Question,
I have an external web server that uses the ReportViewer dll to point to a
Report Server located internally - Not visible to the outside world just to
the intranet. I get a page not found error when trying to view a report via
the reportviewer dll. I have a feeling this is being caused because the
serverurl property is set to point to the server inside the firewall. I can
run the web app just fine from the intranet but whenever I try externally I
get that page not found problem. I was under the impression that the Report
Server Dll was an ASP.Net server control and would run on the server but it
seems as if it is somehow tied to the client. The reason I think this is it
seems as if the client is looking for localhost which of course doesnt exist
on the clients end. Any help and or tips would be appreciated.
Thanks,
Scott EguiresHI, Scott:
I have the same issue. I have a external web cluster to host my website. And
I use the reportview web control to embed the report to my website. My report
server is internally. It works ok from inside, but from outside, I get the
result "The page can not be display". I think it can not find the server.
Did you solve your problem finally? And how did you solve it?
Thanks a lot.
-summer
"Scott Eguires" wrote:
> Question,
> I have an external web server that uses the ReportViewer dll to point to a
> Report Server located internally - Not visible to the outside world just to
> the intranet. I get a page not found error when trying to view a report via
> the reportviewer dll. I have a feeling this is being caused because the
> serverurl property is set to point to the server inside the firewall. I can
> run the web app just fine from the intranet but whenever I try externally I
> get that page not found problem. I was under the impression that the Report
> Server Dll was an ASP.Net server control and would run on the server but it
> seems as if it is somehow tied to the client. The reason I think this is it
> seems as if the client is looking for localhost which of course doesnt exist
> on the clients end. Any help and or tips would be appreciated.
> Thanks,
> Scott Eguires|||Yes I did. I wrote my own report viewer control to view the reports
externally without having to pay for an extra SQL Server license. It was a
real pain but it works beautifully and has a fairly nice interface. I still
need to add security to it though.
Scott Eguires
"summer" wrote:
> HI, Scott:
> I have the same issue. I have a external web cluster to host my website. And
> I use the reportview web control to embed the report to my website. My report
> server is internally. It works ok from inside, but from outside, I get the
> result "The page can not be display". I think it can not find the server.
> Did you solve your problem finally? And how did you solve it?
> Thanks a lot.
> -summer
> "Scott Eguires" wrote:
> > Question,
> >
> > I have an external web server that uses the ReportViewer dll to point to a
> > Report Server located internally - Not visible to the outside world just to
> > the intranet. I get a page not found error when trying to view a report via
> > the reportviewer dll. I have a feeling this is being caused because the
> > serverurl property is set to point to the server inside the firewall. I can
> > run the web app just fine from the intranet but whenever I try externally I
> > get that page not found problem. I was under the impression that the Report
> > Server Dll was an ASP.Net server control and would run on the server but it
> > seems as if it is somehow tied to the client. The reason I think this is it
> > seems as if the client is looking for localhost which of course doesnt exist
> > on the clients end. Any help and or tips would be appreciated.
> >
> > Thanks,
> >
> > Scott Eguires|||Do I need an extra SQL license if I only install the Reoprt server on the web
server, and keep the Report database on another machine with already has a
SQL license?
Do you mind to tell me how you build your own report viewer? Did you use SOAP?
Thanks a lot.
"Scott Eguires" wrote:
> Yes I did. I wrote my own report viewer control to view the reports
> externally without having to pay for an extra SQL Server license. It was a
> real pain but it works beautifully and has a fairly nice interface. I still
> need to add security to it though.
> Scott Eguires
> "summer" wrote:
> > HI, Scott:
> >
> > I have the same issue. I have a external web cluster to host my website. And
> > I use the reportview web control to embed the report to my website. My report
> > server is internally. It works ok from inside, but from outside, I get the
> > result "The page can not be display". I think it can not find the server.
> >
> > Did you solve your problem finally? And how did you solve it?
> >
> > Thanks a lot.
> >
> > -summer
> > "Scott Eguires" wrote:
> >
> > > Question,
> > >
> > > I have an external web server that uses the ReportViewer dll to point to a
> > > Report Server located internally - Not visible to the outside world just to
> > > the intranet. I get a page not found error when trying to view a report via
> > > the reportviewer dll. I have a feeling this is being caused because the
> > > serverurl property is set to point to the server inside the firewall. I can
> > > run the web app just fine from the intranet but whenever I try externally I
> > > get that page not found problem. I was under the impression that the Report
> > > Server Dll was an ASP.Net server control and would run on the server but it
> > > seems as if it is somehow tied to the client. The reason I think this is it
> > > seems as if the client is looking for localhost which of course doesnt exist
> > > on the clients end. Any help and or tips would be appreciated.
> > >
> > > Thanks,
> > >
> > > Scott Eguires|||Yes you do need another SQL Server license in this scenario. That is why I
wrote my own Report Manager/Viewer. I can give you more information on
Monday or Tuesday of next week as I am currently out of town on a business
trip. You can email me at scott@.eguires.net for further discussions if you
wish and I can show you what I have done thus far and you can give me your
opinion on it.
Thanks,
Scott Eguires
"summer" wrote:
> Do I need an extra SQL license if I only install the Reoprt server on the web
> server, and keep the Report database on another machine with already has a
> SQL license?
> Do you mind to tell me how you build your own report viewer? Did you use SOAP?
> Thanks a lot.
> "Scott Eguires" wrote:
> > Yes I did. I wrote my own report viewer control to view the reports
> > externally without having to pay for an extra SQL Server license. It was a
> > real pain but it works beautifully and has a fairly nice interface. I still
> > need to add security to it though.
> >
> > Scott Eguires
> >
> > "summer" wrote:
> >
> > > HI, Scott:
> > >
> > > I have the same issue. I have a external web cluster to host my website. And
> > > I use the reportview web control to embed the report to my website. My report
> > > server is internally. It works ok from inside, but from outside, I get the
> > > result "The page can not be display". I think it can not find the server.
> > >
> > > Did you solve your problem finally? And how did you solve it?
> > >
> > > Thanks a lot.
> > >
> > > -summer
> > > "Scott Eguires" wrote:
> > >
> > > > Question,
> > > >
> > > > I have an external web server that uses the ReportViewer dll to point to a
> > > > Report Server located internally - Not visible to the outside world just to
> > > > the intranet. I get a page not found error when trying to view a report via
> > > > the reportviewer dll. I have a feeling this is being caused because the
> > > > serverurl property is set to point to the server inside the firewall. I can
> > > > run the web app just fine from the intranet but whenever I try externally I
> > > > get that page not found problem. I was under the impression that the Report
> > > > Server Dll was an ASP.Net server control and would run on the server but it
> > > > seems as if it is somehow tied to the client. The reason I think this is it
> > > > seems as if the client is looking for localhost which of course doesnt exist
> > > > on the clients end. Any help and or tips would be appreciated.
> > > >
> > > > Thanks,
> > > >
> > > > Scott Eguires