M
maitakeboy
I am having an issue with my Blackberry users. When they enter an appointment
in their BB, it shows up in Outlook with the Start Time an hour later than
what they created and what shows on the BB. I successfully installed all the
DST2007 patches back in March 2007 and had no issues. However, I had an issue
with my Exchange 2000 server 3 weeks ago, and it was solved by applying the
latest Exchange SP3 update rollup, KB870540, which set my cdo.dll at version
6.0.6603.0. I applied this patch to my BB server too, since it had the
Exchange System Manager. This seems to be when users started noticing the
issue of the calendar appointments with mismatched start times.
RIM support, which exhaustively checked my BES server and found it in
perfect working order, tells me that the cdo.dll version I now have somehow
does not "include" the DST patch, and must be repaired! However, when I check
my registry on the Exchange and BES servers (both Windows server 2000 SP4, I
know I know, get it updated), it shows the DynamicDST subkey under the
TimeZone Key, which I'm told is the definitive test of whether the DST patch
has been applied.Also, my servers have always shown the correct time, and
still do now.
So my question is, does the KB870540 update somehow disable the DST patch?
Is there an established procedure for reapplying the DST after applying the
KB870540 update?
Thanks.
in their BB, it shows up in Outlook with the Start Time an hour later than
what they created and what shows on the BB. I successfully installed all the
DST2007 patches back in March 2007 and had no issues. However, I had an issue
with my Exchange 2000 server 3 weeks ago, and it was solved by applying the
latest Exchange SP3 update rollup, KB870540, which set my cdo.dll at version
6.0.6603.0. I applied this patch to my BB server too, since it had the
Exchange System Manager. This seems to be when users started noticing the
issue of the calendar appointments with mismatched start times.
RIM support, which exhaustively checked my BES server and found it in
perfect working order, tells me that the cdo.dll version I now have somehow
does not "include" the DST patch, and must be repaired! However, when I check
my registry on the Exchange and BES servers (both Windows server 2000 SP4, I
know I know, get it updated), it shows the DynamicDST subkey under the
TimeZone Key, which I'm told is the definitive test of whether the DST patch
has been applied.Also, my servers have always shown the correct time, and
still do now.
So my question is, does the KB870540 update somehow disable the DST patch?
Is there an established procedure for reapplying the DST after applying the
KB870540 update?
Thanks.