What steps will reproduce the problem?
1. Pause or stop the SQL Server service
2. Configure Elmah for both SQL Server and e-mail logging
3. Go to a webpage that tries to access the database
What is the expected output? What do you see instead?
In the e-mail, I expect to see the stack trace for the original
exception. Sometimes I do, but sometimes I get one similar to this (the
Sql error varies depending on the error):
System.Data.SqlClient.SqlException: Timeout expired. The timeout period
elapsed prior to completion of the operation or the server is not
responding.
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection
(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection
(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Elmah.SqlErrorLog.Log(Error error) in
c:\builds\ELMAH\src\Elmah\SqlErrorLog.cs:line 157
at Elmah.ErrorLogModule.LogException(Exception e, HttpContext context)
in c:\builds\ELMAH\src\Elmah\ErrorLogModule.cs:line 120
Sometimes I get the original error in addition to 10 to 40 of these with
the same timestamp. I could filter these out, but just today I got one of
these with no e-mail of the original error, which is more troubling. Does
Server.GetLastError() change if Elmah causes an exception while logging to
the database?
What version of the product are you using? On what operating system?
Elmah 1.0.11211.0, Windows Server 2008, IIS 7
Original issue reported on code.google.com by gentryb...@gmail.com on 22 Feb 2010 at 11:35
Original issue reported on code.google.com by
gentryb...@gmail.comon 22 Feb 2010 at 11:35