elmah / bootstrapper

Configuration-free registration of ELMAH & more

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 $

bootstrapper's Issues

In-Memory Error Log Does Not Display Application Name

When you don't specify a storage mechanism no name is displayed on the error log page:

I've got the app name in my web.config:

<appSettings>
  <add key="elmah:applicationName" value="My App Name Here" />
</appSettings>

but it looks like line 283 doesn't pass any configuration into MemoryErrorLog Class:

     : new Func<ErrorLog>(() => new MemoryErrorLog()));

Unless I missed something I think this could be fixed by passing config to MemoryErrorLog.

Thanks!

Make ErrorFilterModule configurable via appSettings

While the ErrorFilterModule is automatically registered, it is not currently configurable without registration of its <errorFilter> configuration section. Consider making it configurable via <appSettings>.

InvalidOperationException: ValueFactory attempted to access the Value property

Hi,

I'm using Bootstrapper from nuget package elmah.bootstrapper.1.0.0-beta5 and from time to time I've got the following exception (couldn't find the stable way to reproduce though).

System.InvalidOperationException: ValueFactory attempted to access the Value property of this instance.
   at System.Lazy`1.CreateValue()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Lazy`1.get_Value()
   at Elmah.Bootstrapper.ErrorLogHandlerMappingModule.OnPostMapRequestHandler(HttpContextBase context)
   at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Usually it happens when I rebuild the project with IISExpress running, trying to F5 gives error, after another F5 in browser - all works fine. If site is running under IIS - i need to recycle the app pool.

If you need more details I can provide them, thanks!

ConnectionStringName via appSettings

I couldn't find any documentation on available keys/customizations to use in appSettings, so forgive me if this exists, but according to the documentation in order to point ELMAH to a database (SQL) you have to duplicate the connectionString with a connectionString named "elmah:sql".

To use one of these, create a connection string entry in your web.config named elmah:LOGNAME where LOGNAME is the error log name minus the ErrorLog suffix (case-insensitive). So to use SqlErrorLog, create a connection string named elmah:sql.

Its probably just pedantic, but I'd rather not duplicate an existing connection string to rename it. Previous versions of ELMAH had this configuration option:

<errorLog type="Elmah.SqlErrorLog, Elmah" connectionStringName=""/>

I realize this is a "Configuration-free" and I'm asking for configuration options.

Thanks, in advance.

Example project

This is so awesome! Would be great with an example application showing how to configure a logger using this code (like the SQL Server logger).

Example of Elmah.ErrorMail.config?

Everyone can provide an example of Elmah.ErrorMail.config? thanks in advance

Great Package for Elmah!

Hi,

The Elmah Bootstrapper is very useful and easy to use!

Glad you made it and keep up the great work 😃

Simple security configuration

Securing error log pages in ELMAH requires considerable configuration in various areas of the web.config. First, there's remote vs. local access:

<elmah>  
    <security allowRemoteAccess="1" />  
</elmah>

Then there's authorization:

<location path="elmah.axd">  
    <system.web>
        <httpHandlers>
            <add verb="POST,GET,HEAD" 
                 path="elmah.axd" 
                 type="Elmah.ErrorLogPageFactory, Elmah" />
        </httpHandlers>
        <authorization>
            <!--
            <allow roles="admin" />  
            <allow roles="dev" />
            -->
            <deny users="*" />  
        </authorization>  
    </system.web>
    <system.webServer>
        <handlers>
            <add name="ELMAH" 
                 verb="POST,GET,HEAD"
                 path="elmah.axd" 
                 type="Elmah.ErrorLogPageFactory, Elmah"
                 preCondition="integratedMode" />
        </handlers>
    </system.webServer>
</location>

These need to be addressed much more simply, hooking in perhaps via IRequestAuthorizationHandler.

Simple configuration for error mailing

While ErrorMailModule is automatically registered on application start-up, there are no conventions for configuring the module over, for example, <appSettings>.

How does the Bootstrapper package compare to Elmah.MVC

The third party Elmah.MVC has always been my go-to package when adding Elmah to an MVC application. However, in doing so, I am not using the bootstrapper.

Both packages provide similar features; no further configuration required after installig, the URL becomes /elmah instead of /elmah.axd, various configurable app settings are introduced, authorization, etc.

When should I use this package instead of Elmah.MVC? Or should both be used at the same time?

elmah.bootstrapper errors Forbidden: Access is denied

I am using elmah.bootstrapper v1.0.1 in my ASP.Net MVC v5 project. Have the following key in web.config -

<appSettings>
  <add key="elmah:web:path" value="/admin/errors" />
</appSettings>
<elmah>
   <security allowRemoteAccess="1" />
</elmah>

It works well in local host. But after hosted in real server, I can not access the errors page. It said -

Forbidden: Access is denied.
What did I miss here?