SqlErrorLog does UTC offset correction twice

[GoogleCodeExporter]

What steps will reproduce the problem?
1. configure MSSQL error logging
2. create unhandled error condition
3.

What is the expected output? What do you see instead?
expect time in UTC (currently this would be ET+5) get UTC+5 (ET+10)

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

Please provide any additional information below.
Suspect problem is in SqlErrorLog.cs:

Class Commands
...
public static SqlCommand LogError(
...
parameters.Add("@TimeUtc", SqlDbType.DateTime).Value = time.ToUniversalTime();

But then the caller does the same thing:
public class SqlErrorLog : ErrorLog
...
public override string Log(Error error)
...
using (SqlCommand command = Commands.LogError( id, this.ApplicationName,
error.HostName, error.Type, error.Source, error.Message,
error.User,error.StatusCode, error.Time.ToUniversalTime(), errorXml))

Apologies in advanced if already fixed.

Cheers.

Original issue reported on code.google.com by saladp...@gmail.com on 21 Nov 2008 at 2:24

[GoogleCodeExporter]

Original comment by azizatif on 21 Nov 2008 at 2:50

• Changed title: SqlErrorLog does UTC offset correction twice
• Added labels: Component-Persistence

[GoogleCodeExporter]

What version of ASP.NET are you using ELMAH 1.0.9414.11 in?

Original comment by azizatif on 21 Nov 2008 at 3:09

• Changed state: NeedsInfo

[GoogleCodeExporter]

Specifically, is this issue appearing when used under ASP.NET 1.x?

Original comment by azizatif on 21 Nov 2008 at 3:14

[GoogleCodeExporter]

This bug has been reproduced using ELMAH v1.0.10617 under ASP.NET 1.x. The time 
recorded in the MS SQL database is indeed at twice the UTC offset.

This bug does not occur under .NET Framework 2.0 or later because the DateTime 
type 
knows its "kind" and ignore the second conversion to UTC.

Thanks for pointing out the potential source of problem in the code.

Original comment by azizatif on 21 Nov 2008 at 3:55

• Changed state: Accepted
• Added labels: Milestone-Release1.0, Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Fixed in r531. Thanks.

Original comment by azizatif on 21 Nov 2008 at 4:02

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by azizatif on 21 Nov 2008 at 7:53

• Added labels: Affects-1.0B3