search

albertocolom / elmah

Automatically exported from code.google.com/p/elmah
Apache License 2.0
0 stars 0 forks source link

Incorrect timestamps #38

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
View elmah.axd on remote server.

What is the expected output? What do you see instead?
Server is in central time zone, however, the footer on the summary screen
and the timestamps for the errors are off by one hour.  Had several users
try viewing the page from separate time zones (CDT/EDT) with same result.

What version of the product are you using? On what operating system?
Version 1.0.9225.2224 on Windows 2003. 

Please provide any additional information below.
Here is the summary section:

"Powered by ELMAH, version 1.0.9225.2224. Copyright (c) 2007, Atif Aziz.
All rights reserved. Server date is Tuesday, 09 October 2007. Server time
is 18:10:13. All dates and times displayed are in the Central Daylight Time
zone."

In this case the time zone name is correct but the time itself isn't (it
was actually 17:10:13 CDT).

Original issue reported on code.google.com by sdgo...@gmail.com on 9 Oct 2007 at 10:04

GoogleCodeExporter commented 8 years ago

Original comment by azizatif on 10 Oct 2007 at 7:13

GoogleCodeExporter commented 8 years ago 
Perhaps this has something to do with the Microsoft Updates for Daylight 
saving? Is 
it applied or not?

Original comment by schoenho...@gmail.com on 10 Oct 2007 at 8:40

GoogleCodeExporter commented 8 years ago 
I checked that and the patches are current.  Also, I wasn't sure if that could 
be the
root cause seeing that, even prior to the 2007 changes, the switch back to CST
wouldn't take place until month-end.

Original comment by sdgo...@gmail.com on 11 Oct 2007 at 1:07

GoogleCodeExporter commented 8 years ago 
Please discard this issue. The problem seems to have been server-specific as an
install on another server in same domain did not reproduce the issue.  Bouncing 
the
problematic server and restarting the time service seems to have taken care of 
the issue.

Original comment by sdgo...@gmail.com on 11 Oct 2007 at 1:13

GoogleCodeExporter commented 8 years ago 
Thanks for the prompt feedback. Discarding the issue.

Original comment by azizatif on 11 Oct 2007 at 3:15