Home / .NET / Logging

Error Logging Modules & Handlers for ASP.NET

ELMAH README Please read this document carefully before using this release of ELMAH as it contains important information. For peer help and support, vists the ELMAH Discussion Group. Report bugs and issues to the issue tracker o
Information
Category: .NET / Logging
Watchers: 30
Star: 297
Fork: 64
Last update: Mar 25, 2023
Resource links
https://elmah.github.io/
https://github.com/elmah/Elmah

ELMAH README

Please read this document carefully before using this release of ELMAH as it contains important information.

For peer help and support, vists the ELMAH Discussion Group. Report bugs and issues to the issue tracker on the project site. Avoid using the issue tracker to seek help with problems you are experiencing in installing or running ELMAH. That is what the discussion group is for.

The best way to get started with ELMAH is to take it for a spin by launching the supplied demo Web site. Simply go the root of your ELMAH distribution and execute the demo.cmd script. The demo Web site requires Microsoft .NET Framework 2.0.

Version 1.0 BETA 3 Notes

Upgrading from ELMAH 1.0 BETA 2(a)

Microsoft SQL Server Error Log

If you are using the Microsoft SQL Server (2000 or later) for your error log then you should re-create the stored procedures found in the supplied SQL script (see SQLServer.sql). The script does not contain DDL DROP or ALTER statements so you will have to drop the stored procedures manually before applying the CREATE PROCEDURE parts of the script. Other than that, there have been no changes to the schema since BETA 2a so existing data in your logs can be left as it is.

Oracle Error Log

The Oracle error log is new in BETA 3, but if you have been compiling ELMAH from sources between BETA 2 and 3 and using Oracle for your error log then you should re-create the ELMAH$Error table, its indicies and related packages using the supplied SQL script (see Oracle.sql in your distribution). The script does not contain any DROP statements so you will have to drop the table and package manually before applying the script. If you wish to preserve the logged error data, you should consider archiving it in a backup. Please read the comments in this script file carefully for hints on users and synonyms. NB The original package has now been split in two to aid in securing the database in enterprise scenarios.

VistaDB Error Log

The VistaDB error log is new in BETA 3, but if you have been compiling ELMAH from sources between BETA 2 and 3 and using VistaDB for your error log then you should delete the .vdb3 file and allow it to be re-created.

Microsoft Access Error Log

The Access error log is new in BETA 3, but if you have been compiling ELMAH from sources between BETA 2 and 3 and using Access for your error log then you should delete the .mdb file and allow it to be re-created.

Version 1.0 BETA 2(a) Notes

Upgrading from GDN-ELMAH or ELMAH 1.0 BETA 1

The configuration sections and entries have changed slightly if you are using GDN-ELMAH, which is the original that was released on GotDotNet. Consult the samples/web.config file to see examples of how the configuration looks like now.

If you are using the Microsoft SQL Server for your error log then you should re-create the ELMAH_Error table, its indicies and related stored procedures using the supplied SQL script (see Database.sql in your distribution). The script does not contain DDL DROP statements so you will have to drop the table and stored procedures manually before applying the script. If you wish to preserve the logged error data, you should consider archiving it in a backup.

$Revision: 511 $

135 Open More issues
Closed

Add a configuration option to allow omitting AUTH_PASSWORD from error logs

Originally reported on Google Code with ID 140

I would love a configuration option for web.config to specify whether or
not to store the value of the AUTH_PASSWORD server variable in error logs,
e-mails, etc. Perhaps this could be done through an attribute on the
security element (or a new element) such as: logPassword="0" or
omitServerVariables="AUTH_PASSWORD" .

This would allow an admin to prevent the logging of user passwords in the
interest of security. Perhaps this could be extended to also allow
specifying variables to omit or mask from the query string, form and
cookies collections (to prevent logging of credit card numbers, for example).

Note: I am aware of the customization mentioned at
http://groups.google.com/group/elmah/browse_thread/thread/48fc5183d1ed931d
but it would be nice to have this be configurable.

Reported by mhenry07 on 2009-10-28 02:32:48

bug Status-Fixed Priority-High Security Milestone-Release1.2SP2 
opened Aug 25, 2015 by atifaziz 40
Closed

Invalid XML character in exception message causes "elmah.axd" to break

Originally reported on Google Code with ID 129

What steps will reproduce the problem?
1. Log an exception whose message contains the character 0x00
2. Elmah.axd displays YSOD (pasted below)


What version of the product are you using? On what operating system?
version 1.1 rc (1.1.11228)


Please provide any additional information below.

Server Error in '/' Application.
'.', hexadecimal value 0x00, is an invalid character. Line 1, position 186.
Description: An unhandled exception occurred during the execution of the 
current web request. Please review the stack trace for more information 
about the error and where it originated in the code.

Exception Details: System.Xml.XmlException: '.', hexadecimal value 0x00, is 
an invalid character. Line 1, position 186.

Source Error:

An unhandled exception was generated during the execution of the current 
web request. Information regarding the origin and location of the exception 
can be identified using the exception stack trace below.

Stack Trace:

[XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 
1, position 186.]
   System.Xml.XmlTextReaderImpl.Throw(Exception e) +90
   System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) +77
   System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar) 
+185
   System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, 
Boolean expand, BufferBuilder internalSubsetBuilder, Int32& charCount, 
EntityType& entityType) +495
   System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, 
BufferBuilder internalSubsetBuilder, EntityType& entityType) +44
   System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean 
isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos) 
+1797749
   System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char 
quoteChar, NodeData attr) +716
   System.Xml.XmlTextReaderImpl.ParseAttributes() +879
   System.Xml.XmlTextReaderImpl.ParseElement() +545
   System.Xml.XmlTextReaderImpl.ParseDocumentContent() +447
   System.Xml.XmlTextReaderImpl.Read() +41
   System.Xml.XmlReader.MoveToContent() +70
   System.Xml.XmlReader.IsStartElement(String name) +15
   Elmah.SqlErrorLog.ErrorsXmlToList(XmlReader reader, IList 
errorEntryList) in c:\builds\ELMAH\src\Elmah\SqlErrorLog.cs:310
   Elmah.SqlErrorLog.GetErrors(Int32 pageIndex, Int32 pageSize, IList 
errorEntryList) in c:\builds\ELMAH\src\Elmah\SqlErrorLog.cs:186
   Elmah.ErrorLogPage.OnLoad(EventArgs e) in 
c:\builds\ELMAH\src\Elmah\ErrorLogPage.cs:76
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Page.ProcessRequestMain(Boolean 
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436

Reported by btoliver721 on 2009-07-28 16:15:10

bug Priority-Medium Status-Fixed Component-Persistence Milestone-Release1.2 
opened Aug 25, 2015 by atifaziz 23
Closed

JScript error filter does not work in Full trust

Originally reported on Google Code with ID 278

What steps will reproduce the problem?
1. Create an ASP.NET Web Application and configure both ErrorLogModule and ErrorMailModule
in Web.config.
2. Try to hack the website using something like "/?<script>" (to throw an HttpRequestValidationException).
3. Verify the error is logged as expected and an email is received from ELMAH.
4. Specify the following filter in Web.config:

  <elmah>
    ...
    <errorFilter>
      <test>
        <jscript>
          <expression>
            <![CDATA[
              // @assembly mscorlib
              // @assembly System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
              // @import System.Web

              // Do not send email notification when hackers attempt something
              // like "http://.../?<script>"
              FilterSourceType.Name == "ErrorMailModule"
                && BaseException instanceof HttpRequestValidationException
              ]]>
          </expression>
        </jscript>
      </test>
    </errorFilter>
  </elmah>

5. Change the website to run in Medium trust:

  <system.web>
    <trust level="Medium" originUrl=".*" />
    ...
  </system.web>

6. Repeat step 2.
7. Verify the error is logged as expected but the email is *not* received (so far,
so good).
8. Change the website to run in Full trust:

  <system.web>
    <trust level="Full" />
    ...
  </system.web>

9. Repeat step 2.
10. Verify the error is logged as expected *and* the email is received (even though
it should have been prevented by the filter).

It appears there is some sort of caching bug in FullTrustEvaluationStrategy when using
FilterSourceType.Name (in other words, FilterSourceType.Name is not evaluated the second
time through when the "ErrorMailModule" context object is passed to the Eval method).

What is the expected output? What do you see instead?

The filter should work the same in Full trust and Medium trust (meaning the error should
be logged, but an email should not be sent from ELMAH due to the filter). Instead of
correctly applying the filter in the Full trust configuration, FilterSourceType.Name
is not evaluated as expected (it appears to be evaluated as "ErrorLogModule" even though
the context object is "ErrorMailModule").

What version of the product are you using? On what operating system?

I have verified this issue occurs in the latest released version of ELMAH (1.2 SP1)
as well as the latest rev (a53a22fcf694 - 2.0.11227.2305).

OS = Windows Server 2008 R2 SP1

Please provide any additional information below.

I will attach a repro solution in a moment (as soon as I have an issue #).

Reported by [email protected] on 2012-02-26 22:52:20

bug Priority-Medium Status-Fixed DotNet-All Component-Filter Affects-1.0 Milestone-Release1.2SP2 Affects-1.1 
opened Aug 25, 2015 by atifaziz 19
Closed

Request Validation errors does not get logged

What steps will reproduce the problem?

  1. Post some data to a page which contains invalid data e.g. <TEXT>something</TEXT> (as default for html button content in IE6)
  2. Elmah executes, but fails with the following stack trace:
System.Web.HttpRequestValidationException (0x80004005): A potentially dangerous Request.Form
value was detected from the client (button="<TEXT>Confirm &amp; ...").
   at System.Web.HttpRequest.ValidateString(String value, String collectionKey, RequestValidationSource requestCollection)
   at Microsoft.Web.Infrastructure.DynamicValidationHelper.ValidationUtility.CollectionReplacer.<>c__DisplayClass12.<ReplaceCollection>b__d(String value, String key)
   at Microsoft.Web.Infrastructure.DynamicValidationHelper.LazilyEvaluatedNameObjectEntry.ValidateObject()
   at Microsoft.Web.Infrastructure.DynamicValidationHelper.LazilyValidatingArrayList.get_Item(Int32 index)
   at System.Collections.Specialized.NameValueCollection.GetKey(Int32 index)
   at System.Collections.Specialized.NameValueCollection.Add(NameValueCollection c)
   at Elmah.Error.CopyCollection(NameValueCollection collection) in c:\dev\pub\ELMAH-1.2-BETA.dist\src\Elmah\Error.cs:line 343
   at Elmah.Error..ctor(Exception e, HttpContext context) in c:\dev\pub\ELMAH-1.2-BETA.dist\src\Elmah\Error.cs:line 132
   at Elmah.ErrorLogModule.LogException(Exception e, HttpContext context) in c:\dev\pub\ELMAH-1.2-BETA.dist\src\Elmah\ErrorLogModule.cs:line 118

What is the expected output? What do you see instead?

The exception should be logged in the normal way

What version of the product are you using? On what operating system?

Version 1.2 Beta

Please provide any additional information below.

Originally reported on Google Code with ID 217

Reported by laingster on 2011-03-24 09:09:09

bug Priority-Medium Status-Fixed Component-Logic Milestone-Release2.0 
opened Aug 25, 2015 by atifaziz 18
Closed

Support other databases such as SQLite

The reliance on stored procs means I can't use ELMAH for other databases.

Personally, I'd like to see ELMAH make use of Subsonic which would buy other db support for free.

However, given the relatively few queries ELMAH has to support, another option might be to have a provider model. One that uses StoredProcs, the other that uses Prepared SQL Queries from code so that it works with Sqlite.

Originally reported on Google Code with ID 25

Reported by @haacked on 2007-07-27 19:01:49

Priority-Medium enhancement Status-Fixed Component-Persistence 
opened Aug 25, 2015 by atifaziz 17
Closed

Stack trace highlighting doesn't work for Mono

Originally reported on Google Code with ID 320

The nice stack trace syntax highlighting doesn't work correctly for stack traces produced
by Mono. I'm assuming the regular expression to match the stack frames just needs to
be tweaked a bit.

Here is an example stack trace from Mono:

System.Web.HttpException: The controller for path '/helloworld' was not found or does
not implement IController.
  at System.Web.Mvc.DefaultControllerFactory.GetControllerInstance (System.Web.Routing.RequestContext
requestContext, System.Type controllerType) [0x00000] in <filename unknown>:0 
  at System.Web.Mvc.DefaultControllerFactory.CreateController (System.Web.Routing.RequestContext
requestContext, System.String controllerName) [0x00000] in <filename unknown>:0 
  at System.Web.Mvc.MvcHandler.ProcessRequestInit (System.Web.HttpContextBase httpContext,
IController& controller, IControllerFactory& factory) [0x00000] in <filename unknown>:0

  at System.Web.Mvc.MvcHandler.BeginProcessRequest (System.Web.HttpContextBase httpContext,
System.AsyncCallback callback, System.Object state) [0x00000] in <filename unknown>:0

  at System.Web.Mvc.MvcHandler.BeginProcessRequest (System.Web.HttpContext httpContext,
System.AsyncCallback callback, System.Object state) [0x00000] in <filename unknown>:0

  at System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.BeginProcessRequest (System.Web.HttpContext
context, System.AsyncCallback cb, System.Object extraData) [0x00000] in <filename unknown>:0

  at System.Web.HttpApplication+<Pipeline>c__Iterator3.MoveNext () [0x00000] in <filename
unknown>:0 
  at System.Web.HttpApplication.Tick () [0x00000] in <filename unknown>:0 


Here is how the same stack trace looks from Microsoft .NET:

System.Web.HttpException (0x80004005): The controller for path '/helloworld' was not
found or does not implement IController.
   at System.Web.Mvc.DefaultControllerFactory.GetControllerInstance((RequestContext
requestContext, Type controllerType))
   at System.Web.Mvc.DefaultControllerFactory.CreateController((RequestContext requestContext,
String controllerName))
   at System.Web.Mvc.MvcHandler.ProcessRequestInit((HttpContextBase httpContext, IController&
controller, IControllerFactory& factory))
   at System.Web.Mvc.MvcHandler.BeginProcessRequest((HttpContextBase httpContext, AsyncCallback
callback, Object state))
   at System.Web.Mvc.MvcHandler.BeginProcessRequest((HttpContext httpContext, AsyncCallback
callback, Object state))
   at System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.BeginProcessRequest((HttpContext
context, AsyncCallback cb, Object extraData))
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute(())
   at System.Web.HttpApplication.ExecuteStep((IExecutionStep step, Boolean& completedSynchronously))

Reported by [email protected] on 2012-12-15 11:12:22

bug Priority-Medium Status-Fixed Component-UI Milestone-Release2.0 
opened Aug 25, 2015 by atifaziz 15
Open

ZAP throw error ELMAH info leak error in java web services and React

Hi,

I run the OWASP ZAP as DAST check on our java and React application and it throw below error, can you please help to get rid off this error.

"desc": "

The Error Logging Modules and Handlers (ELMAH [elmah.axd]) HTTP Module was found to be available. This module can leak a significant amount of valuable information.

",

Thanks in advance,

Br, Tanmoy

opened Nov 15, 2022 by tanmoyrsc 0
Open

How to add password on /Elmah endpoint?

I implemented elmah in an api, it is working perfectly, but I would like to protect the endpoint, so that only I have access through a username and password

opened Feb 17, 2022 by lopesclayton 0
Open

Make logging of some values configurable (eg don't log the ASPXAUTH cookies to avoid session hijacking)

Has anyone ever actioned making some variables configurable - as per this commentin Troy Hunt's excellent article on the subject of session hijacking Elmah?

Even if I restrict access to elmah logs to single person, that person should not be able to impersonate users. While better than opening your fly to the whole world, it is still not acceptable by any serious standards. The real solution would be to have Elmah NOT store the values of auth/roles cookies BY DEFAULT and make that list configurable

opened Mar 27, 2019 by PandaWood 0
Open

Include session data in the error object (would be useful in ErrorMail_Mailing event handler)

I was looking to use the session data in the ErrorMail_Mailing event handler in global.asax (yes still using asp.net webforms). However, there's no access to session data in the error object and therefore is't not accessible from the ErrorMailEventArgs. After searching for a while i found others encountered this issue too and found Stefan Egli answer on stackoverflow (https://stackoverflow.com/questions/2685657/add-a-session-variable-or-custom-field-to-the-elmah-error-log-table) for how to add session data in the error object. I added it to my cloned solution and it worked.

Is there a reason this functionality isn't included in Elmah? should I create a pull request to add it?

opened Nov 6, 2018 by yornstei 0
Open

Prettier stack trace without async state machine frames

Hey,

Any chance we can apply some of this to clean up all the async junk in stack traces?

dl-ygz4umaa47tb

Inspired by this tweet by @davkean

help welcome enhancement 
opened Oct 12, 2017 by kfrancis 2
Open

Is it wrong to use DelegateHandlers for ApiController Binding Errors?

I was not able to log type binding errors into Elmah.

My ApiController method was:

        [HttpGet, Route("api/om/{NumOM}")]
        public OM ObterInfoOM(decimal NumOM)
        {
            ....
        }

And the wrong request was: http//{host}/api/om/notanumberstringthatfailsmymethod

So, the controller was not able to bind the parameters of my method (logically), giving the following error response (not an exception, but 400 response)

{
    "Message": "The request is invalid.",
    "MessageDetail": "The parameters dictionary contains a null entry for parameter 'NumOM' of non-nullable type 'System.Decimal' for method 'selene.scanpack.infrastructure.Pack`1[selene.scanpack.domain.Entity.OM] ObterInfoOM(System.Decimal)' in 'selene.scanpack.WebApp.Controllers.OMController'. An optional parameter must be a reference type, a nullable type, or be declared as an optional parameter."
}

But unfortunatelly elmah's webapi filter (ElmahRequestValidationErrorFilter) just catched "after binding" errors.

So I was using this implementation as workaround:

    /// <summary>
    /// MessageHandler to intercept WebApi calls that results in 400 status code and was not handled
    /// </summary>
    public class APIHandler : DelegatingHandler
    {
        protected override Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
        {
            try
            {
                return base.SendAsync(request, cancellationToken).ContinueWith((task) =>
                {
                    if (task.IsFaulted)
                    {
                        ErrorLog.GetDefault(HttpContext.Current).Log(new Error(task.Exception));
                    }
                    else if (task.Result.StatusCode == HttpStatusCode.BadRequest)
                    {
                        var error = task.Result.Content.ReadAsAsync<object>().Result as HttpError;

                        if (error != null)
                        {
                            HttpException exc = new HttpException((int)task.Result.StatusCode, error.MessageDetail);
                            ErrorLog.GetDefault(HttpContext.Current).Log(new Error(exc));
                        }
                    }

                    return task.Result;
                });

            }
            catch (Exception e)
            {
                TaskCompletionSource<HttpResponseMessage> tsc = new TaskCompletionSource<HttpResponseMessage>();
                ErrorLog.GetDefault(HttpContext.Current).Log(new Error(e));
                return tsc.Task;
            }
        }
    }

Is this implementation right?

opened May 24, 2017 by emmanuelpereira 0

v2.0-alpha-1(Mar 9, 2018)

NuGet Package

This is the first pre-release of version 2.0 primarily in support of issue #418.

Contents

    dotnet Provides a set of libraries which add service API versioning to ASP.NET Web API, OData with ASP.NET Web API, and ASP.NET Core.
    SoftwareAteliers ASP.NET Core Vue Starter CLI 3.0 @SoftwareAteliersASP.NET Core Vue Starter CLI 3.0 A Vue starter template using Vue CLI 3.0 with custom configuration (default TypeScript, Vue, Router, Vuex, Vuetify) integrated with ASP.​NET Core by @SoftwareAteliers (September 2018)
    MiniProfiler A simple but effective mini-profiler for ASP.NET (and Core) websites
    dotnet ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
    damienbod ASP.NET Core scheduling with Quartz.NET and SignalR
    mubaidr SPA-asp.net-api-vuejs- - A Vue.js single page application for basic task Management & messaging using ASP .NET Webapi 2 and SQL server
    hivokas Request handlers for Laravel
    vlinx-io A lite go logging component
    microsoft .NET 6 reference application shown at .NET Conf 2021 featuring ASP.NET Core, Blazor, .NET MAUI, Microservices, and more!
    iolevel WordPress compiled to .NET Standard. SDK for ASP.NET Core.
    dotnet Blazor is a .NET web framework using C#/Razor and HTML that runs in the browser with WebAssembly.
    danijelh Multi-page ASP.NET Core Vue with TypeScript - Multi-page ASP.NET Core Vue, Typescript, Vuex, Vue router, Bulma, Sass and Jest application. Template/starting point on how to use Vue.js as a multi page(multiple mini spa's) application in .NET Core MVC.
    sachinl0har My First Web Application in ASP.NET MVC with CURD Operation.
    necojackarc JavaScript extensible custom error that can take a message and/or an Error object
    LXSMNSYC Unstyled, dev error overlays for SolidJS
    lamondlu A sample about how to create a dynamic plugins mechanism with ASP.NET Core Mvc at runtime. This sample is based on .NET Core 3.1 and .NET 5
    Seldaek Sends your logs to files, sockets, inboxes, databases and various web services
    SapphireDb SapphireDb Server, a self-hosted, easy to use realtime database for Asp.Net Core and EF Core
    benaadams Blocking Detection for ASP.NET Core
    aspnetcorehero Clean Architecture Solution Template for ASP.NET Core 5.0. Built with Onion/Hexagonal Architecture and incorporates the most essential Packages your projects will ever need. Includes both WebApi and Web(MVC) Projects.
    kriasoft Cross-platform web development with Visual Studio Code, C#, F#, JavaScript, ASP.NET Core, EF Core, React (ReactJS), Redux, Babel. Single-page application boilerplate.
    Share this repo

    Related Repos


    Logging
    6.1k
    Serilog is a diagnostic logging library for .NET applications.
    serilog Serilog is a diagnostic logging library for .NET applications. It is easy to set up, has a clean API, and runs on all recent .NET platforms. While it's useful even in the simplest applications, Serilog's support for structured logging shines when instrumenting complex, distributed, and asynchronous applications and systems.
     
    Logging
    1.2k
    HttpReports is an APM (application performance monitor) system for .Net Core.
    dotnetcore HttpReports is an APM (application performance monitor) system for Net Core. Based on MIT open source protocol, The main functions include statistics, analysis, visualization, monitoring, tracking, etc，It is very suitable for use in microservices.
     
    Logging
    18
    A plug-in that counts the usage of .NET application resources
    itsvse A plug-in that counts the usage of .NET application resources, including: CPU usage, GC, thread status, support for obtaining status information through web requests (access paths and authentication can be customized), and data will be returned in JSON format.
     
    Logging
    142
    .NET logging to Notepad
    yaakov-h This is a library for .NET / .NET Core to log your program's output to a handy Notepad window!
     
    Logging
    5.8k
    NLog - Advanced and Structured Logging for Various .NET Platforms
    NLog NLog is a free logging platform for .NET with rich log routing and management capabilities. It makes it easy to produce and manage high-quality logs for your application regardless of its size or complexity. It can process
     
    Popular
    Logging
    5.8k
    NLog - Advanced and Structured Logging for Various .NET Platforms
    nlog NLog is a free logging platform for .NET with rich log routing and management capabilities. It makes it easy to produce and manage high-quality logs for your application regardless of its size or complexity. It can process
     
    Logging
    53
    Windows log viewer for log4j
    ihtfw Logazmic Minimalistic log viewer for nlog. Supports only log4j xml layout yet. Core is based on Log2console. UI is rewritten in WPF with usage of MahApps.Metro Supports: Listening on tcp/udp Opening *.log4j f
     
    Logging
    297
    Error Logging Modules & Handlers for ASP.NET
    elmah ELMAH README Please read this document carefully before using this release of ELMAH as it contains important information. For peer help and support, vists the ELMAH Discussion Group. Report bugs and issues to the issue tracker o