Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, November 5, 2007 10:51 PM
I am getting the following eroor , when using the UpdatePanel of Ajax
Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server.
The status code returned from the server was: 500
To my strange ,the error is thrown not all the time , only in some rare cases which could not be found out .
I tried to increase the AsyncPostBackTimeout to 300 which was 60 but i could n't get the error down
installing the ajax set up in server is must or not ? We just placed the ajax dlls in the server.
Please can anybody help me with right solution.
Regards
G Suresh Kumar
All replies (21)
Tuesday, November 6, 2007 9:06 AM ✅Answered
Error 500 is a generic catch-all server error that say "hey, something went wrong and I can't fulfill your request." You can examine your server log files to find out the exact cause of the error. This is a server error so it really can't be prevented in your code, but it can be handled. Read http://www.asp.net/AJAX/Documentation/Live/ClientReference/Sys.WebForms/Exceptions/PageRequestManagerServerErrorException.aspx for an explanation of ways to handle the error.
When you ask a question, remember to click "mark as answered" when you get a reply which answers your question.
Tuesday, November 6, 2007 1:56 PM ✅Answered
You can do something like this to improve the user's experience when that occurs: http://encosia.com/2007/07/18/how-to-improve-aspnet-ajax-error-handling/
Ultimately, what you really need to do is add error logging in your application, so you can find out what exception is being thrown. Log4net, for example.
Tuesday, November 6, 2007 10:22 PM
Wednesday, November 7, 2007 8:46 AM
Chetan, that's a totally different error. PageRequestManagerServerError, not the parser error.
Wednesday, November 7, 2007 11:05 PM
Hi Chetan ,
If you know the solution or the cause for that error please post it here
Regards
G Suresh Kumar
Thursday, November 8, 2007 11:57 AM
Try adding ValidateRequest="false" to you Page directive.
-Damien
Wednesday, July 23, 2008 8:57 AM
Wow, Its great. Its working good.
Can you please tell me the details about ValidateRequest statement.
Thanks...
Thursday, October 2, 2008 4:06 PM
I had the similar issue, and happened to solve it by assigning the web site to a new AppPool. (I'm using IIS 6.0)
Monday, March 9, 2009 2:14 AM
There are chances also you get these error due to session timeout
Wednesday, September 23, 2009 4:00 PM
Wow, Its great. Its working good.
Can you please tell me the details about ValidateRequest statement.
Thanks...
this worked for me too,thanks
guys be carefull when you write or read resticted chars (<,>,/ e.g)
Thursday, October 15, 2009 2:25 PM
Very BAD idea. Leaves your system open for script injection attacks. Sorry I don't have the answer, but I suggest you do not use the ValidateRequest="false" directive.
Simon
Try adding ValidateRequest="false" to you Page directive.
-Damien
Thursday, October 29, 2009 2:41 PM
I received this same error just now working with one of our internal tools...
Wednesday, November 4, 2009 6:01 PM
I'm getting this same error, and the weird thing is it literally just started happening. My code was running fine this morning and I made no changes and now suddenly I'm getting the error.
Wednesday, November 4, 2009 6:23 PM
Nevermind, I got mine working.
Tuesday, December 22, 2009 9:30 AM
Introduction
Raised by the PageRequestManager class to return an error when the server returns an error to the browser.
Remarks
When an error occurs on the server while the request is being processed, an error response is returned to the browser and a PageRequestManagerServerErrorExceptionobject is created by using the Error.create function. To customize error handling and to display more information about the server error, handle the AsyncPostBackError event and use the AsyncPostBackErrorMessage and AllowCustomErrorsRedirect properties. For an example of how to provide custom error handling during partial-page updates, see Customizing Error Handling for UpdatePanel Controls.
Tuesday, February 2, 2010 3:10 AM
Try This Code;
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" ValidateRequest="false" %>
Friday, February 12, 2010 12:18 AM
Hi,
I m also facing the same problem in my application.
my problem is something diff.
we are more than 1 person in a team.
I have developed a page, in which i am generating the controls dynamically with some validation controls(AJAX).
its running fine on my machine, but not running on the other developers machine.
i m not able to solve this issue.
Please help me to solve this.
Friday, February 12, 2010 4:18 AM
Hi friends,,
I have solved my above problem...
I was getting the "The status code returned from the server was: 500" Error on my partners machine, but not at my machine,at my machine everything is working fine.
solution : -
i have commented following line in web.config file
<sessionState mode="StateServer" stateConnectionString="tcpip=127.0.0.1:42424" cookieless="false" timeout="120">
and now its working fine at each machine.
May be helpful.
Thank you
Tuesday, August 31, 2010 12:31 PM
Wow, Its great. Its working good.
Can you please tell me the details about ValidateRequest statement.
Thanks...
this worked for me too,thanks
guys be carefull when you write or read resticted chars (<,>,/ e.g)
I had problem with < and > in the 'value' of 'option' in 'select' tag in html (The asp.net dropdown list has a few < and > in few of its selectedvaluefield values and setting the validaterequest=false worked for me!)
Tuesday, November 30, 2010 9:47 AM
Hello Im Try this Code
ValidateRequest="false"
but unfortunately The Error Is Appear for Now
Friday, February 4, 2011 8:01 AM
With me the problem persists. I Tryied use those things and these continues.