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
Thursday, March 10, 2011 6:35 AM
Hi,
ScriptResource.axd:938Uncaught Sys.WebForms.PageRequestManagerServerErrorException: Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 500
That ScriptResource.axd refers to MicrosoftAjaxWebForms.debug.js
I'm googling the issue from hours but I've still has no idea about how it occurs. Weird thing is I do not get any error, but another user of the system most of the time gets this error. -and we both use same web browser.
2/3 places where she gets this error, I used Response.Redirect() with a button.
I really need help and guidance to find what causes this problem.
Thanks
All replies (7)
Monday, March 14, 2011 6:32 PM âś…Answered
the fastest way to get your issue resolved is to talk to your hosting provider and check on server end, they have the responsibility to help you with this issue. Because it's not quite easy to fix 500 error without access to server.
Thursday, March 10, 2011 10:04 AM
Hi,
From the status code 500, it seems to be a server error either in processing request or the server is too busy.
Is your machine hosting IIS for this application ?
Thursday, March 10, 2011 10:18 PM
Unfortunately, "500" is a catch-all exception that just says, "Something went wrong on the server, but we don't know what."
Please refer to this:
How to handle error 500?
An error with status code 500 indicates that there is a problem when the server tries to process the request. There can be variant causes. The problem is how to find out the real cause of the error.
Here are two ways to find it out:
1. Set a breakpoint in the code that is responsible for processing the request, then debug through it to find out the exception being thrown;
2. The real error message is usually returned in the response. We can use an HTTP Sniffer (e.g., Fiddler) to peek into the traffic between the client and server to find out the error message.
Friday, March 11, 2011 3:13 AM
Is your machine hosting IIS for this application ?
No,another machine is hosting IIS for this application. I don't think server is too busy, only few people are using this application.
Friday, March 11, 2011 3:19 AM
chetan.sarode thank you for reply,
But ,How can I debug the application even I cannot observe the problem, on my computer everything works OK.
Friday, March 11, 2011 3:19 AM
dup
Sunday, March 13, 2011 11:49 PM
Hello
You may narrow down this issue by commenting out where this error comes out. Leave only one place of where the error produces and see in what context, this comes up.