<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
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.
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.
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.
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.
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.
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 $