Exception handling in Controller in ASP.Net MVC 4 with ELMAH and ajax

Question

I've seen a number of posts and articles but am not able to see the solution crisply.

I've installed Elmah.MVC via NuGet and have commented out this line from FilterConfig.cs:

//filters.Add(new HandleErrorAttribute());

So that Elmah would pick up the errors.

It works when I provide an invalid action name and I get a yellow page as well as an email.

I want to know about two other types of errors that my code may generate... how are we supposed to handle them:

1.E.g. if my repository or manager (business logic) layer throws an exception when trying to access database or send an email etc.

a. Is the correct way to NOT implement any kind of try catch in Controllers (or anywhere else for that matter) and let Elmah take care of exceptions?

b. If so, and if it shows a yellow error page, how can we show a view of our own liking?

2.If my view contains ajax calls, e.g. via jqgrid, and behind the scenes there are errors, I've noticed they also get picked up properly by Elmah. But how do I show some kind of an error message to the user as well?

Thanks

I found part of the answer here: http://stackoverflow.com/questions/16479396/asp-net-mvc-global-error-handling-with-elmah-best-practices?rq=1 — Raza Ali, Aug 12 '13 at 15:57
Getting closer: I placed a try catch block in controller. In the catch, I wrote 2 lines: 1. Elmah.ErrorSignal.FromCurrentContext().Raise(ex) 2. return View("../Error/ShowException", ex)...... Now I need to address point #2 and also find how to customize 404 error page — Raza Ali, Aug 13 '13 at 06:46

Raza Ali · Accepted Answer · 2013-08-13T13:30:52.960

Here is what I did:

In controller, I placed try catch:

        try
        {
            //model = getmodelfromdb();

            return View("MyView", model);
        }
        catch (Exception ex)
        {
            Elmah.ErrorSignal.FromCurrentContext().Raise(ex);
            return View("../Error/ShowException", ex);
        }

For custom view for 404, I did this in global.asax:

    protected void Application_OnError( )
    {
        var exception = Server.GetLastError( );

        Elmah.ErrorSignal.FromCurrentContext().Raise(exception);

        Helper.SetSessionValue(SessionKeys.EXCEPTION, exception);

        Response.Redirect( "~/Error/ShowException");
    }

For jqgrid, I did this in my controller:

    [HttpPost]
    public ActionResult ListRecords( int page , DateTime? fromdate , DateTime? todate)
    {

               try
               {
                 var list = FetchListFromDB();

            var result = new
                {
                    total = Math.Ceiling(list.Count / (decimal)Helper.PAGE_SIZE),
                    page = page, //--- current page
                    records = list.Count, //--- total items
                    rows = list.List.Select(x => new
                    {
                        id = x.EntityID,
                        cell = new string[] 
                {
        x.Property1,
                    x.Property2
                }
                    }).ToArray()
                };


            return Json(result, JsonRequestBehavior.AllowGet);
        }
        catch (Exception ex)
        {

            var result = new
            {
                errorMessage = "An unexpected error occurred while fetching data. An automatic email has been generated for the support team who will address this issue shortly. Details: " + ex.Message,
                records = 0
            };

            Elmah.ErrorSignal.FromCurrentContext().Raise(ex);

            return Json(result, JsonRequestBehavior.AllowGet);
        }

And this in the View (in the jqgrid definition):

        loadComplete:function(data)
        {
            if (data.errorMessage)
            {
                alert(data.errorMessage);
            }
        },

In a general ajax scenario:

        success: function(data)
        {
            if (data.errorMessage)
            {
                alert(data.errorMessage);
            }
            else
            {
                           //...
            }
        },

This will work, but I would *strongly* advise against `catch (Exception ex)` unless you do it very carefully. Catch the specific exception types you're expecting; you never know when this might catch some other exception and prevent it from getting to its proper handler, or from reaching somewhere it'll make sense to you when debugging. I'd also advise against showing the users your exception messages; you don't want to expose the details of how your application works. Best case scenario is that it'll mean nothing to them; worst case is that it helps a malicious user understand your system. — anaximander, Aug 13 '13 at 10:42

score 2 · Answer 2 · answered Aug 13 '13 at 09:56

a. Is the correct way to NOT implement any kind of try catch in Controllers (or anywhere else for that matter) and let Elmah take care of exceptions?

I'd say that Elmah doesn't "take care" of exceptions, it records them. Ideally, you should try to handle the errors - by all means log them, but also add logic to deal with them so that they don't interrupt the user's workflow.

I'd wrap logic in try blocks, and in the catch use

Elmah.ErrorSignal.FromCurrentContext().Raise(exception);

to record anything that goes wrong. Immediately after that line, however, I'd then do something to try to recover from the exception - catch specific exception types, never just catch (Exception e), and deal with them after logging them. The idea is that you should be reviewing your logs, working out what's causing the exceptions, and improving your program so that it doesn't throw exceptions any more.

To show your own error pages, there's the HandleErrorAttribute, or if you don't want to use that there's also the controller's OnException() method, which is called when a controller action method quits with an exception rather than finishing normally. An ExceptionContext object is passed into that method, so you can use that to get the exception that was thrown and log it, do any cleanup that might be required etc.

Please comment on my approach in the answer I posted to my own question. Thanks — Raza Ali, Aug 13 '13 at 10:38

score 0 · Answer 3 · answered May 15 '15 at 12:39

I know i'm very late to the party but I stumbled upon this answer while searching something similar form Google.

I don't like using try catch blocks everywhere in my code, especially in web apps. I let Elmah catch everything and log it behind the scenes. Then in the web.config file you can redirect based on the error type...

 <customErrors mode="RemoteOnly" defaultRedirect="~/Error" >
  <error statusCode="500" redirect="~/Error"/>
  <error statusCode="404" redirect="~/NotFound"/>
</customErrors>

Exception handling in Controller in ASP.Net MVC 4 with ELMAH and ajax

3 Answers3

Linked