Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / April 2008

Tip: Looking for answers? Try searching our database.

WebPage Timeout

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Peter - 21 Apr 2008 05:59 GMT
ASP.NET 2.0

I have a webpage which calls a webservice this webservice creates reports
and sometime might take 5 minutes to create a report, but the webpage times
out after 90 seconds, it is also using AJAX UpdateProgress control which
stops after 90 seconds.

How can I extend the timeout for the webpage?

Thank You

Peter
Jialiang Ge [MSFT] - 21 Apr 2008 09:46 GMT
Hello Peter,

90 seconds is the default AsyncPostBackTimeOut property value of
ScriptManager. To solve the problem, we can increase the timeout by adding
the property AsyncPostBackTimeOut to the script manager:

<asp:ScriptManager ID="ScriptManager1" runat="server"
AsyncPostBackTimeOut="600" >
</asp:ScriptManager>

Please have a try and let me know if it works for you.

Regards,
Jialiang Ge (jialge@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
ThatsIT.net.au - 21 Apr 2008 09:48 GMT
Server.ScriptTimeout = aNumber

> ASP.NET 2.0
>
[quoted text clipped - 8 lines]
>
> Peter
bruce barker - 21 Apr 2008 16:27 GMT
there is no reliable way to have the browser wait 5 minutes for a response. a
server push might work, you turn off buffering and send a bit of data and a
flush every second.

a better approach is to queue the report and poll for completion.

-- bruce (sqlwork.com)

> ASP.NET 2.0
>
[quoted text clipped - 8 lines]
>
> Peter
Peter - 21 Apr 2008 20:04 GMT
Thank you!!

I will pursue this solution.

> there is no reliable way to have the browser wait 5 minutes for a
> response. a
[quoted text clipped - 19 lines]
>>
>> Peter

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.