Report Timeout

I have a report I execute from an Asp.Net front-end. The report is rendered
directly to PDF via a web services call to the Reporting Services web
service. For this particular report, at exactly 3 minutes, the report always
aborts processing and redirects to a "Page Cannot Be Displayed". The Report
Server log file at this time shows IsClientConnected...Orphan Request
detected or something like that. When I run the report via Report Manager,
everything works fine. I do specify a timeout value of 2400000 in my Asp.Net
where I'm consuming the web service. I've looked at almost every other
timeout but since it works fine in Report Manager, I am inclined to believe
the problem is in my Asp.Net code. Any ideas?Open your Reporing service's web service reference file and in the
constructor
add: "this.Timeout=......"
Works for web service access method.
"AdamB" <AdamB@.discussions.microsoft.com> wrote in message
news:290174E9-D359-4376-9EC7-591FC3421D74@.microsoft.com...
>I have a report I execute from an Asp.Net front-end. The report is
>rendered
> directly to PDF via a web services call to the Reporting Services web
> service. For this particular report, at exactly 3 minutes, the report
> always
> aborts processing and redirects to a "Page Cannot Be Displayed". The
> Report
> Server log file at this time shows IsClientConnected...Orphan Request
> detected or something like that. When I run the report via Report
> Manager,
> everything works fine. I do specify a timeout value of 2400000 in my
> Asp.Net
> where I'm consuming the web service. I've looked at almost every other
> timeout but since it works fine in Report Manager, I am inclined to
> believe
> the problem is in my Asp.Net code. Any ideas?|||I'm not sure where this file is that you are referring to. Also, in my
Asp.Net where I am consuming the web service, I am doing the following:
Dim rs As New WebService (where WebService is the name of my reference to
the Reporting Service ws)
rs.Timeout = 2400000
"Oleg Yevteyev" wrote:
> Open your Reporing service's web service reference file and in the
> constructor
> add: "this.Timeout=......"
> Works for web service access method.
> "AdamB" <AdamB@.discussions.microsoft.com> wrote in message
> news:290174E9-D359-4376-9EC7-591FC3421D74@.microsoft.com...
> >I have a report I execute from an Asp.Net front-end. The report is
> >rendered
> > directly to PDF via a web services call to the Reporting Services web
> > service. For this particular report, at exactly 3 minutes, the report
> > always
> > aborts processing and redirects to a "Page Cannot Be Displayed". The
> > Report
> > Server log file at this time shows IsClientConnected...Orphan Request
> > detected or something like that. When I run the report via Report
> > Manager,
> > everything works fine. I do specify a timeout value of 2400000 in my
> > Asp.Net
> > where I'm consuming the web service. I've looked at almost every other
> > timeout but since it works fine in Report Manager, I am inclined to
> > believe
> > the problem is in my Asp.Net code. Any ideas?
>
>|||Ok, I think you're talking about the Reference.vb file but I have no idea
where this timeout setting is supposed to go.
Adam
"Oleg Yevteyev" wrote:
> Open your Reporing service's web service reference file and in the
> constructor
> add: "this.Timeout=......"
> Works for web service access method.
> "AdamB" <AdamB@.discussions.microsoft.com> wrote in message
> news:290174E9-D359-4376-9EC7-591FC3421D74@.microsoft.com...
> >I have a report I execute from an Asp.Net front-end. The report is
> >rendered
> > directly to PDF via a web services call to the Reporting Services web
> > service. For this particular report, at exactly 3 minutes, the report
> > always
> > aborts processing and redirects to a "Page Cannot Be Displayed". The
> > Report
> > Server log file at this time shows IsClientConnected...Orphan Request
> > detected or something like that. When I run the report via Report
> > Manager,
> > everything works fine. I do specify a timeout value of 2400000 in my
> > Asp.Net
> > where I'm consuming the web service. I've looked at almost every other
> > timeout but since it works fine in Report Manager, I am inclined to
> > believe
> > the problem is in my Asp.Net code. Any ideas?
>
>|||"AdamB" <AdamB@.discussions.microsoft.com> wrote in message
news:D19C1C10-7F24-4834-9EAC-7A20650CE348@.microsoft.com...
> I'm not sure where this file is that you are referring to. Also, in my
> Asp.Net where I am consuming the web service, I am doing the following:
> Dim rs As New WebService (where WebService is the name of my reference to
> the Reporting Service ws)
> rs.Timeout = 2400000
Ok - seems like it is correct - just be sure to set that Timeout property on
every instance of "ws" you are creating.
More simple way is to open the reference file you correctly identified in
another post and place "rs.Timeout = 2400000"
in the constructor. In that case you wouldn't have to set that property on
every instance of "ws" you're creating.
I hope, you know what the constructor is.
There are a couple more places to check.
1. You can set in Page_Load method of your page
Server.ScriptTimeout=2400
2. Do it globally in machine.config or web.config
<configuration>
<system.web>
<httpRuntime executionTimeout="2400"
................................/>
in addtion of what you have already done.