[c13]

Hey all its that time again and though I'd pre-empt the discussions seeing into the future and the issue which is going to occur next week via the CDO.dll

for those of you who are unware, if you don't have one of the latest versions of CDO of you BB server then you may possibly experience an issue next week ( i.e WC 23/10/06) where you calendar appointments are 1 hour out. this has happend over the last few years and reaps havok for your senior directors, and guess who's in the firing line? yep you guessed its you!

look at the below articles, they explaing the issue. its basically to do with a know issue with the CDO.DLL. for next week until the clocks move back this will incorrectly report calendar invites. You don't believe me? check some of next weeks calendar invites. oh you are effected

ask for the below from MS and this should resolve you issues.




Meetings are unexpectedly moved one hour ahead in the last week of October in Exchange Server 2003 2003

Appointments that are rendered by Cdohtml.dll are wrong by one hour during October 2004 for the 'GFT' time zone in Exchange 2000 Server or in Exchange Server 2003

Meetings are unexpectedly moved one hour ahead in Exchange 2000 Server

Meetings are unexpectedly moved one hour ahead or one hour behind in Exchange Server 5.5 for 5.5

[slimbim]

So if I register the latest version of cdo.dll on the BES server, we won't be affected by this problem? at least not on the BES side? Which is the latest version fo cdo.dll?

[Frank Castle]

I just applied the hotfix across exchange mb and the BES ..

CDO.dll - 6.5.7650.8

[PhanMan]

hmmm. This only affects meeting invites or current appointments as well?

i like how in the first article they post

"This problem will occur next in the year 2010."

[#james.power]

We had this issue last year so will apply the hotfix this year. i remember it didnt affect exisiting appointments but can anyone remember what happened to a appointment set for later in that year that was entered in the week the problem occurred.
If that makes sense

[BBAdmin]

I applied the patch on my Exchange this morning. It's a strange one becuase the MS KB states:

Only apply it to systems that are experiencing this specific problem

Now to me that says only install it if you notice the issue affecting you. I saw no harm in being pro-active on this one so I've already run the update.

Everything seems fine afterwards. The patch stops the Information Store while it installs but you don't need to reboot the Exchange afterwards which makes it a low outage fix. The only thing I noticed was that it changed the CDO version on my Exchange (which is what I was expecting). I thought I might have to change the CDO version on my BES to match it up but it appears to work without me having to do so, therefore I'm leaving it for now.

I've had a lot of queries from clients with one question which I thought was obvious but perhaps not, so for clarity you only install this on the Exchange server, not the BES.

[bertiebassett]

ok it's stupid question time..oin this article

Meetings are unexpectedly moved one hour ahead in the last week of October in Exchange Server 2003

it doesn't actually make the hotfix available..anyone know a link where the correct cdo.dll can be downloaded.

ta
bb

[BBAdmin]

OK, I'm going to put these up but I may be told to take them down so grab them while you can.

Here's the Exchange 2000 patch:

http://hotfixv4.microsoft.com/Exchan...U_i386_zip.exe

When you extract it you will need to enter this password: [#@a-mF+

Here's the Exchange 2003 patch:

http://hotfixv4.microsoft.com/Exchan...U_i386_zip.exe

When you extract it you will need to enter this password:]Aon@OU6

The passwords are set by Microsoft and are only valid for the next 5 days (so you basically have to do this before Tuesday)

[bertiebassett]

I had to the manual CDO.DLL copy to BB server and re-register as outlined here.

http://www.blackberryforums.com/bes-...cdo-issue.html

in order to solve the problem.

[BBAdmin]

To be fair I wouldn't want to just switch a CDO version. I'd install the full patch if I were you. If it was just a new CDO you needed then that's what Microsoft would have released, not a full patch.

[bertiebassett]

Sorry BBAdmin my post was a little cryptic, to clarify:

I ran the full MSFT patch on the Exchange server, which I expected to resolve the issue based on your post above, however following testing this didnot seem to solve the problem.

Therefore I copied the new CDO.DLL from the Exchange to the BB server and re-registered as outlined in the link. This seemed to solve the problem.

[BBAdmin]

Interesting. I guess admins need to be aware that they may possibly need to copy the new CDO from their Exchange to their BES servers and register it there too. I had to email about 60 BES clients this morning with all the info (so i don't get a ton of phone calls Monday week), so I'll be interested to see the results.

[PhanMan]

I did not patch my exchange 2003 sp2 box and haven't seen any issues regarding previous or newly created appointments created via bes or owa being off by an hour. Hmmm, guess I'll have to wait and see tomorrow if someone complains.

[slimbim]

This is weird... The hotfix was applied to exchange servers this weekend, and just now I was going to copy the cdo.dll to the BES server and reregister it, but checking on the cdo.dll version, the one on BES is already 6.5.7650.8. Last week it was not, and there is no one that would've done the cdo.dll copy other than me....

[BBAdmin]

I did not patch my exchange 2003 sp2 box and haven't seen any issues regarding previous or newly created appointments created via bes or owa being off by an hour.

Of course you won't have the problem yet!!

[bertiebassett]

Originally Posted by BBAdmin

Of course you won't have the problem yet!!

Er well he might...when i was testing on friday pre-upgrade any appointments made for this week were out by 1 hour - which suggests that any appointments customer might have made from their BB's a couple of weeks ago would an hour wrong as well.

so far no calls..

[PhanMan]

Originally Posted by bertiebassett

Er well he might...when i was testing on friday pre-upgrade any appointments made for this week were out by 1 hour - which suggests that any appointments customer might have made from their BB's a couple of weeks ago would an hour wrong as well.

so far no calls..

Yesterday was the 4th Sunday of October so that is when I believe the incorrect cdo time decrement would have been applied. Clocks will be turned back officially this Sunday (October 29th, 2006). I don't understand how I wouldn't be experiencing this issue now if it was occurring.