Time stamp is an hour off

Archived Topics
1

I believe since DST has occurred, we have been experiencing a BIZZAR tstamp issue.

When running a query directly from MySQL:

SELECT 
ID,
crew,
start_time,
stop_time 
FROM rotation_schedule 
WHERE start_time BETWEEN '2010-04-22 07:00:00' AND '2010-04-22 19:00:00' 
ORDER BY ID

I return:

[quote]“ID”,“crew”,“start_time”,“stop_time”
“223”,“4”,“2010-04-22 07:00:00”,“2010-04-22 18:59:59”
“224”,“3”,“2010-04-22 19:00:00”,“2010-04-23 06:59:59”[/quote]

When ran in FPMI I return:

[quote]“ID”,“crew”,“start_time”,“stop_time”
“223”,“4”,“2010-04-22 08:00:00”,“2010-04-22 19:59:59”
“224”,“3”,“2010-04-22 20:00:00”,“2010-04-23 07:59:59”[/quote]

I have checked the TZ on both client and gateway. Both are Central (GMT -06:00). Both system clocks are the same as well.

Also, on the “Date Range” component, the blue arrow reprenting “NOW” is an hour behind.

But, here is the KICKER, IF, I change my clock on the Client to read an HOUR later than it really is, then the arrow is correct, yet my query from above still results in the same problem.

Any ideas guys? :laughing: :prayer:

2

Have you checked your project’s time zone setting? This is independent of a machine’s time zone. To find it, open the FactoryPMI Designer and make sure the cursor is at the very top of the tree in the Project Browser. This will then display the project’s properties in the Property Editor - the first standard property is Time Zone. You can set the project to use either the Gateway’s or the Client’s time zone, or you can set it to a static time zone.

3

Yes, sorry, I should have posted that too. I have ALL of my projects set to use the GATEWAY’S TZ. Also, Regarding the query I posted about, if i do a SELECT NOW() on a dynamic property, it returns the Tstamp correct, but the query mentioned above does not. And the arrow on the time range component doesn’t either.

4

How odd… If you hadn’t posted about the TZ I would suspect that one machine is set to -6 Indiana… not -6 central… If memory serves they don’t Do dst there.

5

The timezones are correct, however the server is not patched correctly for daylight savings time. That is where the 1-hour discrepancy is from.

6

Travis, when you say Server patched, what do you mean exactly?

7

Be sure your PC’s (Travis mentions the server(s) running the Gateway and MySQL, but this should be done for all PC’s) are updated for the ‘new’ DST changes

http://support.microsoft.com/kb/955839/