Ajax – Asp.net 4.0 UpdatePanel error: Sys.WebForms.PageRequestManagerServerErrorException: The status code returned from the server was: 12002

ajaxasp.netasp.net-4.0updatepanelupdateprogress

I have a process that takes about 15-20 seconds to executed and at the end it updates a updatepanel to refresh a gridview

But it keeps me bringing me this error:

Microsoft JScript runtime error: Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 12002

I have extensively searched for answers everywhere and they keep pointing to this

httpRuntime maxRequestLength="1024000" executionTimeout="999999"
and AsyncPostBackTimeout ="360000" in the ToolkitScriptmanager

It doesn't work for me, can anybody please suggest anything that will help me?
Here are part of the code:

<%@ Page Title="" ....AsyncTimeout="36000" EnableEventValidation="false" ValidateRequest="false" %>
<asp:ToolkitScriptManager ID="ToolkitScriptManager1" runat="server" AsyncPostBackTimeout ="360000" >
</asp:ToolkitScriptManager>
<asp:UpdatePanel ID="UpdatePanel1" runat="server" UpdateMode="Conditional">
<ContentTemplate>
<asp:Button ID="BtnGeneraPed" runat="server" Text="GP" Height="45px" Width="148px"/>
<asp:UpdateProgress ID="UpdateProgress1" runat="server">
<ProgressTemplate>
<table>
<tr><td><img alt="Cargando" src="../images/loading.gif" /></td></tr></table>
</ProgressTemplate>
</asp:UpdateProgress>
<asp:GridView ID="GV" runat="server" BackColor="White" 
......
</asp:GridView>
</ContentTemplate>
</asp:UpdatePanel>

Best Answer

So after almost 2 days I finally could figure this out...

It was extremely simple... I was testing and developing this in a machine with Windows XP and IE 8.... I tested it in Firefox and Chrome and the results where positive, no error

The issue was related to ReceiveTimeout settings from internet explorer 8.. it was to short

The solutions is in this article:
http://intersoftpt.wordpress.com/2009/06/23/resolve-page-cannot-be-displayed-issue-in-ie8/

Related Solutions

Asp.net-mvc – A potentially dangerous Request.Form value was detected from the client

I think you are attacking it from the wrong angle by trying to encode all posted data.

Note that a "<" could also come from other outside sources, like a database field, a configuration, a file, a feed and so on.

Furthermore, "<" is not inherently dangerous. It's only dangerous in a specific context: when writing strings that haven't been encoded to HTML output (because of XSS).

In other contexts different sub-strings are dangerous, for example, if you write an user-provided URL into a link, the sub-string "javascript:" may be dangerous. The single quote character on the other hand is dangerous when interpolating strings in SQL queries, but perfectly safe if it is a part of a name submitted from a form or read from a database field.

The bottom line is: you can't filter random input for dangerous characters, because any character may be dangerous under the right circumstances. You should encode at the point where some specific characters may become dangerous because they cross into a different sub-language where they have special meaning. When you write a string to HTML, you should encode characters that have special meaning in HTML, using Server.HtmlEncode. If you pass a string to a dynamic SQL statement, you should encode different characters (or better, let the framework do it for you by using prepared statements or the like)..

When you are sure you HTML-encode everywhere you pass strings to HTML, then set ValidateRequest="false" in the <%@ Page ... %> directive in your .aspx file(s).

In .NET 4 you may need to do a little more. Sometimes it's necessary to also add <httpRuntime requestValidationMode="2.0" /> to web.config (reference).

Ajax – Sys.WebForms.PageRequestManagerServerErrorException: …. The status code returned from the server was: 404

Ok, I have managed to find a solution ... minutes after posting.

I used HTTPWatch to get the URL the request was being posted to. This showed me the URL was Appending to the existing URL each post and not overwriting. I used some JavaScript at the top of my page to set the forms URL to the window location:

Sys.Application.add_load(function()
{
    var form = Sys.WebForms.PageRequestManager.getInstance()._form;
    form._initialAction = form.action = window.location.href;
});

This sorted it.

Hope it helps someone else.

Best Answer

Related Solutions

Asp.net-mvc – A potentially dangerous Request.Form value was detected from the client

Ajax – Sys.WebForms.PageRequestManagerServerErrorException: …. The status code returned from the server was: 404

Related Topic