Wednesday, March 21, 2012
Reports: Internet access
2000 running on a different intranet server ( http://myrs2000). For some
time, we have exposed some RS reporting using the ReportViewer object on
several intranet web applications as well as within Sharepoint portal server
with no problem at all.
Now, there's a need to expose one RS report over the internet within a
webapplication hosted on our webserver. The first attempt was to use the
ReportViewer object that we've used in the past; something like the following:
<cc1:ReportViewer id="rv" runat="server"
ServerUrl="http://myrs2000/reportserver" ReportPath="/SalesReport
Width="850px" Height="600px"></cc1:ReportViewer>
We this application (webpage) is accesed via the intranet, everything works
fine; but it doesn't when accesed over the internet. Instead of displaying
the report-manager-window in a frame; we get something like "Internet
explorer cannot open this page".
Then I found that an additional tag (ReportServerExternalUrl) had to be
added to the RSWebApplication.config; although probably this has notting to
do with the ReportViewer object.
Then I added a web reference to the ReportServer webservice
(http://myrs2000/reportserver/reportservice.asmx) and then added some c# code
to render the reporting on the web page and everything works fine (even from
the Internet); it's just that this reports has some complexity (e.g liked
reports) and thefore it's best to display it with the ReportViewer object.
Apart for having to add some code for the webservice call to work, like
adding network credentials; why this approach works and the other doesn't?
Any ideas as to what it's missing from the first approach (ReportViewer) ?
Why is it not working?
Is it neccesary to add the ReportServerExternalUrl with a value something
like http://myReportPortal,com for the ReportViewer object to work? And use
this value in the ServerUrl of the report viewer property ?
Thanks in advance.
Regards,
CesarOn Nov 2, 1:27 pm, Cesar <Ce...@.discussions.microsoft.com> wrote:
> We have our webserver (http://www.mywebserver) and the reporting services
> 2000 running on a different intranet server (http://myrs2000). For some
> time, we have exposed some RS reporting using the ReportViewer object on
> several intranet web applications as well as within Sharepoint portal server
> with no problem at all.
> Now, there's a need to expose one RS report over the internet within a
> webapplication hosted on our webserver. The first attempt was to use the
> ReportViewer object that we've used in the past; something like the following:
> <cc1:ReportViewer id="rv" runat="server"
> ServerUrl="http://myrs2000/reportserver" ReportPath="/SalesReport
> Width="850px" Height="600px"></cc1:ReportViewer>
> We this application (webpage) is accesed via the intranet, everything works
> fine; but it doesn't when accesed over the internet. Instead of displaying
> the report-manager-window in a frame; we get something like "Internet
> explorer cannot open this page".
> Then I found that an additional tag (ReportServerExternalUrl) had to be
> added to the RSWebApplication.config; although probably this has notting to
> do with the ReportViewer object.
> Then I added a web reference to the ReportServer webservice
> (http://myrs2000/reportserver/reportservice.asmx) and then added some c# code
> to render the reporting on the web page and everything works fine (even from
> the Internet); it's just that this reports has some complexity (e.g liked
> reports) and thefore it's best to display it with the ReportViewer object.
> Apart for having to add some code for the webservice call to work, like
> adding network credentials; why this approach works and the other doesn't?
> Any ideas as to what it's missing from the first approach (ReportViewer) ?
> Why is it not working?
> Is it neccesary to add the ReportServerExternalUrl with a value something
> likehttp://myReportPortal,comfor the ReportViewer object to work? And use
> this value in the ServerUrl of the report viewer property ?
> Thanks in advance.
> Regards,
> Cesar
The Report Manager and SSRS require domain user access to work
correctly. The web service allows for a trusted domain user account to
be used (i.e., network credentials), where as the report viewer
control does not default to an internal domain user account. You can
try either setting the connection to an internal domain account
programmatically during the rendering of the report viewer -or- use
the SSRS web service to export the report to a predefined format and
then view it in a web page. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant
Monday, March 12, 2012
Reports asking for username and password
I have two questions -
1. I have deployed the reports on our webserver. When I access the link http://servername/Reports from IE it asks me for a username and password the first time. I tried all the passwords including admin user/pwd but the dialog remains there. I close IE and start again I can access the reports. For your information, the checkbox 'Save my password' is checked in the reports. Does anyone know why the username/password dialog appears the first time?
2. Sometimes some of us get a 'Page cannot be displayed' while the others can access it. I have to start Reporting services and everyone can access the reports. Any ideas?
Thanks!!
Kind of sounds like the same problem we had when I started deploying reports out to the server. We were accessing the Report server through another program that I was using to hold the reports to make it easier for the customers to access them without going out of the original program
What we done was build a dummy account on our intranet and put that in Security portion of the Report Manager and set it so that was the password for users to access the system without having to have them type in their Windows Password or whatever password your administrator has set up to access the server.
Make sure the box is checked under the security to store the password on the server if that's how you're going to do it, otherwise it doesn't matter whether you have the Save password box checked or not the server won't save it.
As far as you have to consistently start Reporting services I don't know. I know ours runs as long as the server is running so it's accessable all the time.
Hope this helps some
|||Wayne,
How did you create a dummy account and attach it to the security portion of the Report Manager. Did you do it through the reporting config tools -> Specify Execution Account.
|||Our system administrator set up the dummy account just like any other Windows account and put in our Doman Users Group which is the group that has access to the majority of the areas.
What we do instead of having to put every user with having access to the sites with their windows logon we put the main user group with rights and then in the Report Manager under the Data Sources/Security you can set whether or not they use windows logon or a password stored on the server and that is where you put in the dummy account User Name and password.
You also have to make sure that the User Groups have rights to not only the reports and the data source but are also on the user permissions for the database itself other wise you will still get an error that they can't access the report. We made the group just as a browser in the report manager so they couldn't do anything and just as a datareader on the database, although they can't access it anyway.
Hope this helps