Hello,

My colleague was using the ScriptManager's AsyncPostBackError event to change an exception message and once this event finished, a JavaScript alert message box was displayed alerting the user. Now, with either the new AJAX 3.5, or .NET 3.5, or Visual Studio 2008, or any combination of the 3, the JavaScript alert does not show up. Instead, Internet Explorer indicates to the user a JavaScript error has occurred and no message box is shown. 

I have read many posts by members stating that the JavaScript alert box shows up and they would like to disable it but I on the other hand would like the message to pop-up. I tried using ScriptManager.RegisterStartupScript to throw an alert box up at the end of the event but that does not seem to do anything at all.

If I use the following in the body of my HTML.. 

<script type="text/javascript">

</script>

This works except my custom error message is displayed along with the Exception type to the left which I cannot remove.

 Example: Sys.WebForms.PageRequestManagerServerErrorException: Please select whether this address is residential or commercial.

I'd like the alert to just say, 'Please select whether this address is residential or commercial'

Does anyone have any idea how I can make this work?

Suggestions and comments are greatly appreciated.

 -- Rick

Hi Rick,

Please do it like this.

<script type="text/javascript" language="javascript">
   Sys.WebForms.PageRequestManager.getInstance().add_endRequest(function(sender, e)
   {
    e.set_errorHandled(true);
    $get("error").innerHTML = "Sorry, an error has occurred: " + e.get_error().message;
    setTimeout(function(){ $get("error").innerHTML = ""; }, 3000);
   });
  </script>

Also , you can see this document.

I hope this help.

Best regards,

Jonathan

Thanks for your help Jonathan. This method will work just not sure why our previous method stopped working. Must have been because of either .NET 3.5 or AJAX 3.5, or both.

Hi Cougar2,

I would like to suggest that you should add debugger to your code and use Visual Studio 2008 to see all the methods and properties.

Best regards,

Jonathan 

You may have figured it out already but I also noticed a change in 3.5 where the AsyncPostBackError wasn't getting handled where it had been just fine in 2.0. Turns out that we had custom Application_Error handling in our global.asax which would redirect to an appropriate error page. While this wasn't getting called in 2.0 it does get called in 3.5. So.. if that's your issue then you'll need to either check for the error type and only redirect on certain types and/or check to see if the current context handler is in an async postback within the Application_Error. If the current page handler is in async postback then don't redirect.

 Hope that helps somebody who is running in to similar problems.