locked
Sys.WebForms.PageRequestManagerTimeoutException RRS feed

  • Question

  • User-743597761 posted

    Hi there,

     I have just installed the new beta. So nothing works again. Don't you just love this beta stuff :-)

     I get a "Sys.WebForms.PageRequestManagerTimeoutException: The server request timed out" when using a updatepanel. Why is that?

    I have placed

    <add verb="GET" path="ScriptResource.axd" type="Microsoft.Web.Handlers.ScriptResourceHandler" validate="false"/>

    in my web.config. What is wrong here?

    Tuesday, November 7, 2006 2:22 PM

All replies

  • User-168160696 posted

    Do you have a particularly long running process on the server? Sounds like the PageRequestManager was waiting for a response and it didn't come back. Did you get that message after 90 seconds? Try setting the ScriptManager.AsyncPostBackTimeout greater than the default value to see if that narrows where the problem is.

     http://ajax.asp.net/docs/mref/f0b6a7c8-cfb9-3c5b-46cc-673488c5bbb7.aspx

     

    Thursday, November 9, 2006 1:39 PM
  • User2106567859 posted

    I solved the issue with a property setting of ScriptManager

    Below an example to set the timeout to 10 hours

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

     I hope it solves your problem in an easy way.

    Sunday, November 19, 2006 7:55 AM
  • User1802187680 posted
    I set the timeout attribute to 36000, and it still times out after 90 seconds exactly. I don't know what the problem could be.
    Thursday, November 23, 2006 2:30 PM
  • User-396192383 posted
    I think your issue is somewhat more complex.  You really should use Fiddler or some other tool to see what the requests are being made and how they are being satisfied.  For example the timeout issue can be a direct result of an image no being found which causing a long running javascript to never get a response.  Hence would be the ideological problem...The problem sometimes is what you experience on the browser in a Ajax environment doesn't have the same characteristics of a normal page.  In a normal page a image not found is merely a image not found but because the Script manager wraps that request - not finding a image could (and will) throw a ton of errors totally not related to what you would of expected.  Why?  most 404 errors have jscript in them and the SCM gets confused when it parses it and this has been an issue since Atlas...So your best defense is to use tools that can indicate where the actual issue is by examining all the browser requests and responses... Probably noit the cookie cutter answer you want - but for the most part - unless you are dealing with 28K dial up customers - setting that timeout value really is not a solution - more of an indication of another problem...
    Thursday, November 23, 2006 4:46 PM
  • User949494092 posted

    Probably you are running a server-side C# code and a client-side-script by a control like a Button all together.

    Or maybe you have written a client-side-script for a control which is placed in an updatePanel.

    <o:p> </o:p>

    Avoid them; your problem will be solved.

    Wednesday, May 9, 2007 6:03 AM
  • User2054115725 posted

    Hi ,

    Im getting the following error...

    Sys.Webforms.pagerequestManagerServerErrorException:An unknown error occurred while processing the request on the server.The status code from the server was 12002.

    How can i fix this problem... 

    I need urgent help..

    Even Though i set the AsyncPostBackTimeout to 36000sec also doesnot fix the problem.

    Wednesday, October 22, 2008 5:03 PM
  • User555306248 posted

    For Sys.WebForms.PageRequestManagerTimeoutException

     

    http://asp.net/ajax/documentation/live/ClientReference/Sys.WebForms/Exceptions/PageRequestManagerTimeoutException.aspx

    http://asp.net/ajax/documentation/live/tutorials/CustomizingErrorHandlingforUpdatePanel.aspx

    To solve this problem we can increase the timeout. You can change the timeout time by adding a new property to the script manager control. This property is called AsyncPostBackTimeOut and it can help us to define the number of seconds before the request will throw a request timeout exception*.

    For example if you want that the timeout will take maximum 10 minutes your code should be look like this:

    <asp:ScriptManager ID="ScriptManager1" runat="server"

    AsyncPostBackTimeOut="600" >

    </asp:ScriptManager>     

    The default value of the AsyncPostBackTimeOut property is 90 seconds.

    and for ServerErrorEXception

    It is not a good practice to use Response.Write from within an ASP.NET page in general. As UpdatePanels work by intercepting the page rendering process you are recieving the errors.

    You can put the code to generate the data in an HTTPHandler or you can make the button a PostBackTrigger.

    Add the following JavaScript:

    Sys.WebForms.PageRequestManager.getInstance().add_endRequest(EndRequestHandler);

    function EndRequestHandler(sender, args)
    {       
               if (args.get_error() != undefined)
               {
                 args.set_errorHandled(true);location.reload(true);
               }
    }

    http://weblogs.asp.net/leftslipper/archive/2007/02/26/sys-webforms-pagerequestmanagerparsererrorexception-what-it-is-and-how-to-avoid-it.aspx

    http://alpascual.com/blog/al/archive/2007/04/26/How-to-fix-Sys.WebForms.PageRequestManagerParserErrorException-in-AJAX.aspx

    http://forums.asp.net/p/1040597/1448046.aspx

    http://forums.asp.net/t/1333182.aspx

    Wednesday, October 22, 2008 11:18 PM
  • User1872958993 posted

    Hi Vijay, Did you get any solution for the problem. Regards Josh

    Wednesday, December 3, 2008 3:47 AM
  • User-2114126289 posted

    I have same problem & i have solved it using three line of code in asp.net

    1) <asp:ScriptManager ID="ScriptManager1" runat="server" AsyncPostBackTimeout ="360000">

    </asp:ScriptManager>

    I think point 1. is more than enough

    2)<httpRuntime executionTimeout="360000"/>

     

    Friday, May 22, 2009 12:37 PM
  • User-2097060974 posted

    Just setting AsyncPostBackTimeout="360000" is good enough.  Basically, you're telling AJAX to keep churning and churning until 6 hours, and then display the error - longer than probably anyone will ever stay on the page to see it.  As long as it's doing everything else it's supposed to, finding the real cause is probably inconsequential.  I saw a post saying to avoid using UpdatePanels with AJAX Timers, that this is the cause.  I believe that's why this was happening for me; but my timer updates the controls in my UpdatePanel just fine now without this error coming up, so I'm happy with this workaround.

    -Tom

    Thursday, December 24, 2009 6:02 PM
  • User-1745935066 posted

    Try this in ur webconfig file.

    </httpHandlers>

                <httpRuntime maxRequestLength="1024000" executionTimeout="999999"/>

                </system.web>    

    </configuration>

     

    Mark as "Answer" if this post is helpful

    Monday, December 28, 2009 1:36 AM