Comments on: Use jQuery to catch and display ASP.NET AJAX service errors

By: Dave Ward

Dave Ward — Fri, 05 Mar 2010 18:35:18 +0000

You can definitely do something like this with MVC, but the implementation won’t be very similar at all. I wouldn’t suggest using this post as a starting point for MVC AJAX error handling.

By: Tim

Tim — Tue, 02 Mar 2010 05:23:10 +0000

How can this be applied to c# and MVC?

I have a controller, not a webmethod so when my controller method throws an exception, the resulting error returned to the browser contains the well formatted HTML error message .Net generates, rather than just the error message the thrown exception returns….

By: Use jQuery to catch and display MR AJAX errors « Chorn Sokun’s Weblog

Use jQuery to catch and display MR AJAX errors « Chorn Sokun’s Weblog — Thu, 01 Oct 2009 17:59:01 +0000

[...] a comment » This post influenced Dave Ward’s post to replicate the behavior that he discussed within MonoRail application. To mimic this behavior [...]

By: Miroslav Ninkovic

Miroslav Ninkovic — Fri, 18 Sep 2009 07:30:13 +0000

Thanks Dave!

By: Dave Ward

Dave Ward — Thu, 17 Sep 2009 21:30:53 +0000

MVC doesn’t return its errors in the same format as ASP.NET AJAX services. That’s normal behavior.

By: Adauto

Adauto — Thu, 17 Sep 2009 17:26:26 +0000

You may be receiving HTML string because the error didn’t came from a thrown exception. I noticed that when it is a Internal Server Error (500) it shows the error page defined.

By: Miroslav Ninkovic

Miroslav Ninkovic — Thu, 17 Sep 2009 14:46:23 +0000

Indeed, a great post. I’m using it to make ASP.NET MVC ajax calls. But there is a ‘little’ issue. The response text in xhr.responseText is HTML string, not JSON string.
To be honest, this sounds normal for me and when server returns JSON string is strange for me :). Apparently is that, since I’m the only one with this problem, I’m missing something. Do you know what?
Thanks!

By: jrummell

jrummell — Tue, 23 Jun 2009 12:17:01 +0000

Yes, you are correct. Changing customErrors to

<customErrors mode="Off" />

fixed it. Thanks!

By: Dave Ward

Dave Ward — Mon, 22 Jun 2009 20:11:26 +0000

I believe the customErrors setting in your web.config controls that.

By: jrummell

jrummell — Mon, 22 Jun 2009 18:08:29 +0000

Hi Dave. Thank you for this awesome post!

I’m running into a problem where I can’t get the exception details when I test a web service from a machine that is not the web server. (machine A has the html page open in a browser that calls a WebService on machine b)

This is what I get:

{"Message":"There was an error processing the request.","StackTrace":"","ExceptionType":""}

I tried changing debug to true in web.config, but that didn’t make a difference. Any ideas?

By: Adauto

Adauto — Thu, 18 Jun 2009 16:45:39 +0000

error: function(result, textStatus, thrownError){
result.responseText.match(/(.*)/i);
MostraCaixa(”AVISO DE ERRO”, error[1] || result.responseText, Botoes.OkAlerta);
$(”.close:visible”).focus();
}

By: Adauto

Adauto — Tue, 16 Jun 2009 16:26:00 +0000

I had the same problem. When the exception comes from an Interval Server Error (500), the StackTrace page is shown. I ended up with two solutions. I could either change the Application_Error or get the error through javascript somewhere in the error page. So i decided to go for the second one. By doing this i don't mess up with the Global.asax. error: function(result, textStatus, thrownError){ result.responseText.match(/(.*)/i); MostraCaixa("AVISO DE ERRO", error[1] || result.responseText, Botoes.OkAlerta); $(".close:visible").focus(); }

By: Ryan

Ryan — Tue, 21 Apr 2009 20:22:39 +0000

Not sure if you noticed, but at the bottom of the BlockUI plugin page is a link to another plugin called jGrowl. The nice thing about it is that it has stackable growls in case you have multiple notifications or a click-happy user.

http://stanlemon.net/projects/jgrowl.html

By: Rick Strahl

Rick Strahl — Mon, 20 Apr 2009 08:56:35 +0000

Dave, nice to see this written up. I’ve long cursed the way that jQuery returns error information because there are a number of things that you have to check for.

I think you need a bit more than what you have here though – if there are HTTP level errors you need to possibly manage status codes in addition to an actual error message that the server returns. Casper’s response points at this although I don’t think there’s really any good solution to a 500 level error.

The error handler I use in an $.ajax() wrapper class looks something like this:

error: function(xhr, status) {
var res = xhr.responseText;
var err = null;
if (res && res.charAt(0) == ‘{‘)
var err = JSON.parseWithDate(res);
if (!err) {
if (xhr.status != 200)
err = new CallbackException(xhr.status + ” ” + xhr.statusText);
else
err = new CallbackException(“Unknown Error Response”);
err.detail = res;
}
else
err = new CallbackException(err); // force error to common format

if (errorHandler)
errorHandler(err, _I, xhr);
}

Like your code i try first to eval the result, but if that fails then looking at the status code and returning the server’s status code usually is more useful. This isn’t going to be helpful on most 500 type errors, but it will be if you have a 40x error for missing or unauthorized content at least.

By: Casper

Casper — Sun, 19 Apr 2009 21:15:13 +0000

I know your handling it on the client side but should you do something with it on the code behind?