Remote Web Report timing out

I've got an internal Reporting Server and I can access the reports directly
there with no problem.
I can generate a report with the WinForm without a problem as well.
What I'm trying to do is to use a second, public web server that has an ASPX
page containing the reportviewer control that connects to the internal web
server so we can implment the seucurity system used by the rest of the web
site.
I can open the report, which has an input parameter without a problem. When
I enter a parameter and attempt to generate the report, it connects to the
Report Server without a problem but then sits there, spinning the little
green arrow until it times out.
With profiler turned on I can see the exact same set of data calls being
made when the report is run on the report server, in the WinForm and in the
WebForm, the only difference being that it appears the WebForm never gets the
data back.
Any ideas?
--
Josef
http://www.reluctantdba.comOn Sep 13, 9:54 am, Josef Finsel
<JosefFin...@.discussions.microsoft.com> wrote:
> I've got an internal Reporting Server and I can access the reports directly
> there with no problem.
> I can generate a report with the WinForm without a problem as well.
> What I'm trying to do is to use a second, public web server that has an ASPX
> page containing the reportviewer control that connects to the internal web
> server so we can implment the seucurity system used by the rest of the web
> site.
> I can open the report, which has an input parameter without a problem. When
> I enter a parameter and attempt to generate the report, it connects to the
> Report Server without a problem but then sits there, spinning the little
> green arrow until it times out.
> With profiler turned on I can see the exact same set of data calls being
> made when the report is run on the report server, in the WinForm and in the
> WebForm, the only difference being that it appears the WebForm never gets the
> data back.
> Any ideas?
> --
> Josefhttp://www.reluctantdba.com
Normally hitting the web server will be slower if it is on another
machine/server. Also, communicating through IIS and a network takes
extra time. The only suggestion I have is to tune the query/stored
procedure that sources the report via the Database Engine Tuning
Advisor. This might give you a little performance improvement. Hope
this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Those are all good and valid points but it turns out that it was actually a
permissions issue.
I got it resolved and it works fine.
Thanks
--
Josef
http://www.reluctantdba.com
"EMartinez" wrote:
> On Sep 13, 9:54 am, Josef Finsel
> <JosefFin...@.discussions.microsoft.com> wrote:
> > I've got an internal Reporting Server and I can access the reports directly
> > there with no problem.
> >
> > I can generate a report with the WinForm without a problem as well.
> >
> > What I'm trying to do is to use a second, public web server that has an ASPX
> > page containing the reportviewer control that connects to the internal web
> > server so we can implment the seucurity system used by the rest of the web
> > site.
> >
> > I can open the report, which has an input parameter without a problem. When
> > I enter a parameter and attempt to generate the report, it connects to the
> > Report Server without a problem but then sits there, spinning the little
> > green arrow until it times out.
> >
> > With profiler turned on I can see the exact same set of data calls being
> > made when the report is run on the report server, in the WinForm and in the
> > WebForm, the only difference being that it appears the WebForm never gets the
> > data back.
> >
> > Any ideas?
> > --
> > Josefhttp://www.reluctantdba.com
>
> Normally hitting the web server will be slower if it is on another
> machine/server. Also, communicating through IIS and a network takes
> extra time. The only suggestion I have is to tune the query/stored
> procedure that sources the report via the Database Engine Tuning
> Advisor. This might give you a little performance improvement. Hope
> this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On Sep 14, 4:02 pm, Josef Finsel
<JosefFin...@.discussions.microsoft.com> wrote:
> Those are all good and valid points but it turns out that it was actually a
> permissions issue.
> I got it resolved and it works fine.
> Thanks
> --
> Josefhttp://www.reluctantdba.com
> "EMartinez" wrote:
> > On Sep 13, 9:54 am, Josef Finsel
> > <JosefFin...@.discussions.microsoft.com> wrote:
> > > I've got an internal Reporting Server and I can access the reports directly
> > > there with no problem.
> > > I can generate a report with the WinForm without a problem as well.
> > > What I'm trying to do is to use a second, public web server that has an ASPX
> > > page containing the reportviewer control that connects to the internal web
> > > server so we can implment the seucurity system used by the rest of the web
> > > site.
> > > I can open the report, which has an input parameter without a problem. When
> > > I enter a parameter and attempt to generate the report, it connects to the
> > > Report Server without a problem but then sits there, spinning the little
> > > green arrow until it times out.
> > > With profiler turned on I can see the exact same set of data calls being
> > > made when the report is run on the report server, in the WinForm and in the
> > > WebForm, the only difference being that it appears the WebForm never gets the
> > > data back.
> > > Any ideas?
> > > --
> > > Josefhttp://www.reluctantdba.com
> > Normally hitting the web server will be slower if it is on another
> > machine/server. Also, communicating through IIS and a network takes
> > extra time. The only suggestion I have is to tune the query/stored
> > procedure that sources the report via the Database Engine Tuning
> > Advisor. This might give you a little performance improvement. Hope
> > this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
Glad you resolved the issue. Let me know if I can be of further
assistance.
Regards,
Enrique Martinez
Sr. Software Consultant

Remote Process of Report

Hi,

We have a reports running in a system in our internal network. Now our requirement is we have to publish the same report into web for the public. How can I do that..?

Note :

I can not install reporting service in my Web server system.

There should be a way to put the report from the reporting server to the web server and display in the webpage to the public.

This is really an urgent requirement.

Are you using RS2005? If so, you can embed the report viewer control into your ASP.Net application.|||

I'm using 2003, Is there any way to do this. My problem is I have to show a report to a website which is running in diffrent system in the same network.

the user will be provided by a hyperlink in the asp.net webpage by clicking the link the user should see the report.

Thanks

Mohan

|||

It is tricky in 2003 without the viewer control.

Your user's won't be authenticated against your RS backend, so you will have to get the contents of the report from within your ASP.Net application. You will want to use the HTMLFragment deviceinfo setting. The trickier part is resolving the secondary streams (like images and charts). You will have to use the StreamRoot deviceinfo to redirect image requests back to your ASP.Net application, so you can make them on behalf of your users.