1 hour off

[KC]

Apologies up front if this is posted to the incorrect group.

The issue actually has to do with with the Calendar on Windows Mobile 5.
Calendar appointments appear to be correct in Outlook 2003. An Exchange 2003
server with Activesync is configured and working (syncing without error).

The issue is that on the mobile device all appointments are off by one hour.
I find it no coincidence that daylight savings time was changed last year and
that these appointments seem to be off only during this new daylight savings
period.

The timezones have been verified on the OS (XP Pro), Outlook 2003 & on the
Mobile device and all match (mountain time).

The daylight savings utility for Windows Mobile has been run on the PDA
device without correction and the tzmove application has been run without any
help.

The windows mobile device has also been rebuilt from scratch without any
changes.

Any thoughts on what may be causing the issue and the steps to correct are
appreciated.

-KC

 

[Brian Tillman]

Apologies up front if this is posted to the incorrect group.

microsoft.public.pocketpc is the correct newsgroup.

The issue actually has to do with with the Calendar on Windows Mobile
5. Calendar appointments appear to be correct in Outlook 2003. An
Exchange 2003 server with Activesync is configured and working
(syncing without error).

The issue is that on the mobile device all appointments are off by
one hour.

You haven't applied the WIndows Mobile 5 DST update.
<http://www.microsoft.com/downloads/...5C-8AC1-4821-81FE-3F4ADA831FE0&displaylang=en>

 

[KC]

Brian, thank you for the response. Although I did verify previously that he
had run the DST update tool for windows mobile directly on his handheld,
since you mentioned the method of running via Activecync I thought that I
should wait and have him try that prior to responding back immediately.

Unfortunately this did not help, and the same condition remains.

I was able to gather a bit more information:
Holidays that happen to be during this *new* DST period are ONLY off one
hour during the new DST period.
However other recurring appointments and recurring events are off one hour
indefinately.

Of course this is leading it to appear that all day appointments span 2 days
since they are incorrectly starting at 11PM the day before or ending 1AM the
day after (At this point I am becoming DST dyslexic)

Just to cover the bases again. this appears to be an isolate issue in our
250+ mailbox exchange environment. Windows and Office are fully patched, the
tzmove application was run last year (as it was intended) however it was also
run recently for good measure without any update.

As I was typing this I realized that I had not asked this user to see what
his calendar looked like via OWA. I wish I had thought of this earlier as
this will tell us which Outlook client is displaying the ‘correct’
information. If it is correct using OWA then the PDA is at fault, if it is
incorrect there as well as on the PDA then its Outlook on the computer.

It appears that there are a growing number of these issues out there as
people are now realizing that there appointments are off by an hour and that
its shifting single day appointments to multiday.

If anyone has any thoughts or suggestions on what the next steps should be
in troubleshooting I would appreciate it.

 

[KC]

I just wanted to follow up with our resolution (ok workaround) on this
currently isolated case of calendar appointments being one hour off when
being viewed on the mobile device.

The workaround (directly from the user):
I deleted the holidays and all day/multi-day appointments that occurred
during the DST period on my computer and re-synced the phone and it brought
them all down correctly. The recurring appointments were all okay to start
with. It looks like everything is now correct. All the appointments
including holidays after the DST period this year were correct to start with.
I looked forward at the holidays in the DST period next year and they were
all okay. We will see what happens when DST is over, if everything gets
screwed up again.

I certainly hope that all the others out there with similar problems do not
face the same fate.