Hello,
I'm trying to view my reports over the internet.
I can browse to https://www.mysite.com/reports and it prompts me to log in
(integrated windows authentication) and I can view my list of reports.
When I click on a report I recieve a basic "The page cannot be displayed"
error.
I even tried just "basic" authentication within IIS but still get the same
error.
The server hosts both components (SQL Server & IIS) on a Windows 2003 SP1.
No special authentication, not a web farm, do I still need to get Enterprise
edition?
Help...
Thanks in advance,
GregCheck your IE address when you open your report, it must point to
http://yourserver/reports. It point to your internal RS, that's why you can
not open report from internet. It shows your list is because IIS is working.
still no clue?
check your config file. RSWebApplication.config under ReportManager
change
<ReportServerUrl>http://yourserver/reportserver</ReportServerUrl>
to
<ReportServerUrl>http://yourserver domain/reportserver</ReportServerUrl>
and then visit
http://your server domain/reports|||Thank you Wei Ming, this solved it for me.
"Wei Ming" wrote:
> Check your IE address when you open your report, it must point to
> http://yourserver/reports. It point to your internal RS, that's why you can
> not open report from internet. It shows your list is because IIS is working.
> still no clue?
> check your config file. RSWebApplication.config under ReportManager
> change
> <ReportServerUrl>http://yourserver/reportserver</ReportServerUrl>
> to
> <ReportServerUrl>http://yourserver domain/reportserver</ReportServerUrl>
> and then visit
> http://your server domain/reports
>|||Also, is there a way during setup that would resolve this?
"Wei Ming" wrote:
> Check your IE address when you open your report, it must point to
> http://yourserver/reports. It point to your internal RS, that's why you can
> not open report from internet. It shows your list is because IIS is working.
> still no clue?
> check your config file. RSWebApplication.config under ReportManager
> change
> <ReportServerUrl>http://yourserver/reportserver</ReportServerUrl>
> to
> <ReportServerUrl>http://yourserver domain/reportserver</ReportServerUrl>
> and then visit
> http://your server domain/reports
>|||I can not give u an answer for this, here is what I am thinking:
during setup, it will gather information from your computer, and save that
piece info into config file, if you can find that information ( for example,
hosts or registry ) and modify it. Your RS can be auto configured after
installation.
What's the peticular reason you like to config this during setup?|||For future deployments, instead of having a client go into a config file, I'd
rather have all of these settings done for them.
I'm curious, how did you find this answer?
"Wei Ming" wrote:
> I can not give u an answer for this, here is what I am thinking:
> during setup, it will gather information from your computer, and save that
> piece info into config file, if you can find that information ( for example,
> hosts or registry ) and modify it. Your RS can be auto configured after
> installation.
> What's the peticular reason you like to config this during setup?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment