Hi Anders,

Have you tried using Elmah (http://elmah.github.io/) or similar tool to review unhandled exceptions?

That is a good idea. I will see if I can get it up an running.

Hi,

I'm working with Anders on the same project and I tried Elmah, but it is only logging unhandled exceptions, and although the error says Unhandled exception it is handled by Episerver.Global, i.e. EpiServer.Global writes to log, and does not throw the excpetion again, so Elmah is not able to catch the exception...

Anybody else have some suggestions ?

If the error is swallowed, you could also attach to the Error event in Global.asax.cs and do some additional logging:

public override void Init()
{
    Error += EPiServerApplication_Error;
    base.Init();
}

private void EPiServerApplication_Error(object sender, EventArgs e)
{
    if (HttpContext.Current == null) return;

    Exception lastError;
    try
    {
        lastError = Server.GetLastError();
    }
    catch
    {
        return;
    }

    if (lastError == null) return;

    // TODO: log error

            
    try
    {
        // TODO: Clear the last error and return correct status code
        Server.ClearError();
        Response.Clear();
        ExceptionManager.RenderHttpRuntimeError(lastError);
        Response.End();
    }
    catch
    {
    }
}

My apologies for 3 posts in a row. Neither Edit nor Delete buttons are working for me :(

Regarding Elmah... Did you configure Elmah correctly?

For example, in Alloy website, if I throw an exception or navigate to a non-existing page, I also get "EPiServer.Global: 1.2.5 Unhandled exception in ASP.NET" in the log file.

But Elmah shows me proper errors.

Can you verify this in your project?

Hi Dejan,

I'll try replay on your 3 posts in 1 post :)

1. I see other like e.g. : System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Code\CXP\SolarB2bEpiserver\SolarB2bEpiserver\App_Data\blobs\b7b5645dddb14cffad7e9806d0451d44\0a9daf6ab794486ca60d4091c6c867d2_Thumbnail.png'.

These appear in both EpiServerErrors.log and Elmah. But the "1.2.5 Unhandled exception in ASP.NET" only appears in log-file

Looking at source code of Episerver.Global (http://world.episerver.com/documentation/class-library/?documentId=cms/7/e9e09ee4-16f6-ec1e-fc40-180b192c7f05) there is this line :

         _log.Error("1.2.5 Unhandled exception in ASP.NET", e);

this makes me think that although it says Unhandled exception, it is actually handled by EpiServer.Global (i.e. written to log), and thus not catched by Elmah, but maybe I'm wrong (see 3) ...???

2. That's what I'm planning to do today :)

just tried this, and lastError = null...

3. I'n not sure I configed Elamh correctly, but if you can catch there "1.2.5 Unhandled exception in ASP.NET" while I don't, it might be configed wrong.... I installed it from NuGet and ran the project... but if you can tell me how to config it... :)

Hi Tarek

We identified the cause of our problems, but we haven't fixed it.

The problem seems to be related to the BVNetwork 404Handler. The 404 handler handles 404 pages, but they are apparantly still raised as unhandled exceptions that the Episerver unhandled exception handler catches. But in this situation, the inner exception is gone, so Episerver doesn't log any details.

I raised an issue on the 404Handler board: https://github.com/BVNetwork/404handler/issues/35, but nobody have replied to my thread.

I don't know if the problem should be fixed by BVNetwork or by Episerver, and we haven't investigated it further. I haven't raised the issue with Episerver Support either.

Our main problem was caused by our operations monitoring that tried to call an alive page that we haden't created on Episerver yet. As the monitoring tool called the page every minute or so, it generated a lot of 404 messages that ended up in the log. This is fixed, so now we only see extra logging of the "real" 404 requests, which is still a problem but more manageable.

Regards

Anders

This was a bug in Episerver error handling which is fixed in the latest versions.