« Previous Next »

• 07-01-2009, 4:11 AM

  bapo_10@hotmail.com Joined on 03-01-2007, 2:06 AM Posts 17

  Scripting error Reply Contact I have my web site up and running. It has debug enabled (I know I shouldn't - but it has), When I connect over a slow connection the system timesout and hangs the application (code behind no longer executes even on re-entry to the site).  The specific error is line 513Sys.Webforms.PagerequestmanagerTimeOutexception: TheServer requestTimedOut and i can drop into the VS debugger to view the error. If I turn off debugging is this gonna cure this problem - it's difficult to repeat and spasmodic in nature!  Any help appreciated.

• 07-01-2009, 10:59 AM

  In reply to

  jeff@zina.com Joined on 09-26-2003, 10:43 AM Naples, FL, USA Posts 2,063	Re: Scripting error Reply Contact bapo_10@hotmail.com: If I turn off debugging is this gonna cure this problem There's an easy way to find out...  :) Jeff Look for Wrox's new book Professional IIS 7 in your local bookstore, or order now at Amazon.com

• 07-06-2009, 4:32 AM

  In reply to

  Leo Tang - MSFT Joined on 12-12-2008, 2:47 AM Posts 783	Re: Scripting error Reply Contact Hi Please check the following article: Sys.WebForms.PageRequestManagerTimeoutException http://msdn.microsoft.com/en-us/library/bb310955.aspx Also, you can get more valuable suggestions at our ASP.Net forum. Leo Tang Microsoft Online Community Support Please remember to mark the replies as answers if they help and unmark them if they provide no help.

• 07-08-2009, 2:09 AM

  In reply to

  bapo_10@hotmail.com Joined on 03-01-2007, 2:06 AM Posts 17

  Re: Scripting error Reply Contact Thanks for the response I implemented the AsyncPostBackTimeout. I'm a bit of a novice at this stuff but if I include something like the following where updateCatchLog is a link to my database of c# caught errors - is this a way of clearing and recording the error. I'm finding it difficult to test because the errors come infrequently. Any further advise on these matters is appreciated .. and thanks again <script language="c#" runat="server" >void Page_Error(object sender, EventArgs e) { try { string errorMessage = "Error occurred" + Server.GetLastError(); Server.ClearError(); throw new ArgumentException(errorMessage); } catch (Exception ex) { funcs.updateCatchLog(ex); } finally { } } </script>