"Terry" <Terry@discussions.microsoft.com> wrote in message
news:F23236CC-7A1E-4906-977C-D06B0029B0F6@microsoft.com...
> Oleg, good morning!
>
> What is the name of the config file did up go into to update the timeout
> value?
>
> Thank you in advance for your assistance.
>
> "Oleg Yevteyev" wrote:
>
>> never mind.
>> I found it - in the constructor of the ReportingService place
>> this.Timeout=........
>> works finally.
>> Thanks.
>>
>> "Oleg Yevteyev" <myfirstname001atgmaildotcom> wrote in message
>> news:ODN80FooFHA.904@TK2MSFTNGP10.phx.gbl...
>> > I'm having the same problem - one of my reports takes about 3 min to
>> > execute.
>> > I tried everything - web server(s) timeouts, report server configs,
>> > report settings, machine.config changes, aspx page
>> > Server.ScriptTimeout -
>> > everything - still getting "The operation has timed-out." error after
>> > about 2 min of execution.
>> >
>> > at
>> > System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest
>> > request) at
>> > System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest
>> > request) at
>> > System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
>> > methodName, Object[] parameters) at ReportingService.Render(String
>> > Report,
>> > String Format, String HistoryID, String DeviceInfo, ParameterValue[]
>> > Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle,
>> > String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed,
>> > Warning[]& Warnings, String[]& StreamIds)
>> >
>> > What exactly did you do to force the Timeout property to 300000?
>> > I cannot find an exact place to set that value.
>> > Thanks.
>> >
>> > "Ben Shaffer" <BenShaffer@discussions.microsoft.com> wrote in message
>> > news:58373C3A-40E6-44D5-B41C-53E865AA7E57@microsoft.com...
>> >> I've been through there and played with plenty of values, but never
>> >> found
>> >> anything that would help with the timeout in my Render call.
>> >>
>> >> I did find a fix to the problem though - not sure if it's the best way
>> >> to
>> >> do
>> >> it:
>> >> I modified my Reference.cs file for the SOAP Web Reference to the
>> >> Report
>> >> Server to force the Timeout property to 300000. I figure that'll give
>> >> my
>> >> app
>> >> 5 minutes before the Render call times out.
>> >>
>> >> "Wayne Snyder" wrote:
>> >>
>> >>> Take a look at rsreportserver.config in the reportserver directory.
>> >>>
>> >>> --
>> >>> Wayne Snyder MCDBA, SQL Server MVP
>> >>> Mariner, Charlotte, NC
>> >>> (Please respond only to the newsgroup.)
>> >>>
>> >>> I support the Professional Association for SQL Server ( PASS) and
>> >>> it's
>> >>> community of SQL Professionals.
>> >>> "Ben Shaffer" <BenShaffer@discussions.microsoft.com> wrote in message
>> >>> news:A26B272B-BA01-4E9E-8ECB-F6AD572E82C5@microsoft.com...
>> >>> > I'm using the Web service library's ReportingService.Render
>> >>> > function
>> >>> > to
>> >>> > export a report to PDF format.
>> >>> >
>> >>> > After 90-100 seconds of processing, the call to Render throws an
>> >>> > exception
>> >>> > saying that "The operation has timed-out", but the ReportServer
>> >>> > keeps
>> >>> > on
>> >>> > grinding at the report. The report is eventually finished
>> >>> > succesfully, as
>> >>> > I
>> >>> > can see in the RS Execution Log that it ends with a status of
>> >>> > 'rfSuccess'.
>> >>> > Data time is under a second, Process time is almost 7 seconds, and
>> >>> > render
>> >>> > time is about 150 seconds. Nothing's timing out on the server
>> >>> > side.
>> >>> >
>> >>> > How do I extend the timeout for the Render call so that my
>> >>> > application
>> >>> > sticks around long enough to get the report from RS?
>> >
>> >
>>
>>
>>