[ppittman]

Hi, trying to locate the CDO.DLL of 6.5.7654.1 as the Exchange servers are currently at 6.5.7655.7 and the BES are still at 6.5.7638.2.

I cant upgrade to exchangemapicdo 1.2.1 as the Exchange admin arent prepared to alter their setup as they have had numerous problems of late.

Exchnagemapicdo 1.2.1 was installed on the BES as the mapi is currently 1.0.2536.0 but the CDO of 6.5.7638.2 was used instead of the newer version as the Exchange servers were at the same level but have since been upgraded. Unfortunately, they didnt inform us!

Or, can i copy the current CDO of 6.5.7655.7 from the exchange server onto the BES and register it?

[CanuckBB]

mapicdo 1.2.1 is the latest. Just install that. Nothing needs to be done to the Exchange server.

[ppittman]

But does that include the CDO of 6.5.8*** which will put the BES higher than the Exchange CDO?

[ppittman]

OK, any problems with having 6.5.8039.0 on the BES and 6.5.7655.7 on the Exchange server?

[knottyrope]

What version of Exchange?

For the most part CDO 1.2.1 is backwards compatable, but I have seen some issues with 2003 and 2007.

I am still using ESM with SP2 applied and ran Microsoft update after (knot windows update).

[ppittman]

Exchange 2003 SP2 at the moment. Unfortunately, we cannot make any changes to the exchange server.

[knottyrope]

you dont need to make any changes to exchange, just on BES server.

KB15779-How to install or upgrade the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1

[ppittman]

For some reason CDO 1.2.1 had already been installed but cdo.dll was currently at version 6.5.7638.2. I think this may have been due to the exchange server having the same on it at the time of the 4.1.6 upgrade but has since had new patches etc. installed.

I have just registered manually the 6.5.8039.0 cdo.dll, rebooted and can see the new setting in the MAGT log files.

Will see if this makes a difference to the DST issue.

And yes it has! Calendar entries entered on the handheld are now displaying at the correct time in the users Outlook and not an hour in front.

[CanuckBB]

I've ran the 1.2.1 package on a BES with 2007 SP@ with no issue.

For a 2003 SP2 install, the safest way is to install ESM SP2 on the BES, and patch BES at the same time as Exchange.

[ppittman]

Couldnt load ESM SP2 as the servers are 64bit.

Just trying to work out why the original BES admin guy would install 1.2.1 but use an old cdo.dll?

Its all working now tho.

[knottyrope]

Originally Posted by ppittman

Couldnt load ESM SP2 as the servers are 64bit.

Just trying to work out why the original BES admin guy would install 1.2.1 but use an old cdo.dll?

Its all working now tho.

Maybe at the times that was the only version and after exchange was patched, it was older than exchange