Daylight Saving a week early?

Forums › Legacy mobile platforms (Windows Mobile, Palm OS, Web OS, Symbian, Meego, Blackberry) › Daylight Saving a week early?

Glazza

279 posts

Ultimate Geek
+1 received by user: 11

Trusted

#7027 13-Mar-2006 11:43

Hi Guys.

I am hoping that someone can shed some light on to this.

We run exchange 2000, with Mobile Information Server 2002, connecting to hp ipaqs (mostly 4150).

All these devices are set to New Zealand timezone, along with Automatically adjust clock for Daylight Saving.

However, come yesterday, appointments on the ipaq are all 1 hour out. if I create an appointment in my calendar for 3:00pm and sync my ipaq, it will appear in my ipaq as 4:00pm

If I change my ipaq to sync directly to my pc, rather than via MIS, the times appear correctly in the ipaq.

Does anyone have any ideas how to fix this... We have some very aggravated management at the moment, whom have missed flights....

Thanks

1 | 2

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#30596 13-Mar-2006 11:48

Yes, this is an old problem, and there's no easy fix for it. You can adjust this by creating the appointments in a different timezone, and this will be adjusted correctly, but only for this week. After this they will be of course shifted - but then they are already gone.

No updates available...

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

Glazza

279 posts

Ultimate Geek
+1 received by user: 11

Trusted

#30598 13-Mar-2006 11:51

Mauricio

Thanks for your reply.

What step in my chain is causing the issue do you know, I am assuming it is something to do with the Mobile Information Server?

Does Exchange 2003, with the MIS stuff built in resolve these issues?

And lastly, does this affect all countries with daylight saving, or just NZ?

Thanks

David

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#30601 13-Mar-2006 12:00

It looks like some settings on Windows Mobile 2003, Windows Mobile 2003 Second Edition have the wrong start and end dates for DST in New Zealand, Australia and some other countries.

I have just checked now and I am not seeing this problem with my Exchange Server 2003 SP2 and Windows Mobile 5.0 devices.

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

Jama

1420 posts

Uber Geek
+1 received by user: 1

Trusted

#30603 13-Mar-2006 12:08

My WM5 appointments are an hour out as well.

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#30604 13-Mar-2006 12:10

Interesting - my Apache and Jasjar are both showing the appointment with their correct time.

Both Regional Settings and Time Zone are set to New Zealand. Check yours, the default Regional Settings is UK...

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

Glazza

279 posts

Ultimate Geek
+1 received by user: 11

Trusted

#30606 13-Mar-2006 12:13

Yup, I just got one of our new ipaq's out, which is WM5, and the same issue is occuring...

jama... in your configuration, do you have Mobile Information Server, or Exchange 2003?

Thanks

HP

Shop now for HP laptops and other devices (affiliate link).

Jama

1420 posts

Uber Geek
+1 received by user: 1

Trusted

#30609 13-Mar-2006 12:53

Exchange 2003 but not all SP2 yet

mike_c

4 posts

Wannabe Geek

#30626 13-Mar-2006 17:22

We are getting this issue with Exchange 2003 SP1; Apache's and Harrier's running Windows Mobile 2003 and Windows Mobile 5.

I have logged this with Microsoft support however they are leaning towards it being an issue with the PDAs... I can't see how that can be if it is occuring on both HP iPaqs and HTC devices...

Would be very interested to hear if anyone makes progress with this...

Mike

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#30628 13-Mar-2006 17:25

mike_c: I have logged this with Microsoft support however they are leaning towards it being an issue with the PDAs... I can't see how that can be if it is occuring on both HP iPaqs and HTC devices...

Mike, this issue is not with a specific PDA, but with the OS. MSFT PSS can't do much, because this requires the involvement of the developer team.

This has happened before and will happen again, next year affecting the USA, since they are changing their DST rules - then perhaps there will be a fix...

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

Glazza

279 posts

Ultimate Geek
+1 received by user: 11

Trusted

#30629 13-Mar-2006 17:51

Mike: I have had a look at the data that is been sent from our Mobile Information Server, and the data is correct, so the error is on the device. Please keep me posted with any additional information

Mauricio: Do you have access to a KB article or anything, I need something from Microsoft to state the issue, failing that, I will have to go thru the process of calling Microsoft....

Surely this must be of importance to MS, this basically makes there devices pointless, even if it is only for 1 week a year...

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#30630 13-Mar-2006 17:56

Unison I don't have a KB on hand for this issue, but the way it works, DST information is stored as part of a .dll, not in the registry like on the desktop version of the OS. That's why is a problem that is not as easy to fix as it would be on the "bigger" version of the OS.

This is an issue that we raised before, and I am passing this to the development team, again today.

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

Geekzone

Want to support Geekzone and browse the site without the ads? Subscribe to Geekzone now (monthly, annual and lifetime options).

Glazza

279 posts

Ultimate Geek
+1 received by user: 11

Trusted

#30633 13-Mar-2006 18:28

Mauricio: The werid thing is that it doesn't effect everyone, ie you are not experiancing the issues that others are.

Please keep us posted to how to get on with Microsoft etc.

Thanks

David

mike_c

4 posts

Wannabe Geek

#30658 14-Mar-2006 00:27

Hi all
Early signs are that Exchange 2003 SP2 has resolved this issue for us; however the appointments need to be modified so that they get re-synched.
Will keep you posted once we have done further testing.
Mike

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#30751 15-Mar-2006 11:42

That could be why I don't see this problem with my Pocket PCs, since I am running Exchange Server 2003 SP2 for a few months now...

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

Jama

1420 posts

Uber Geek
+1 received by user: 1

Trusted

#30754 15-Mar-2006 11:52

That is why having fixed DST dates is and always has been a bad idea. MS need to allow us to edit the DST start/end dates or add our own DST dates on the device.

I did suggest this once when in a con call to Redmond.

1 | 2