[cayzac]

I'm having problems with contacts sync'ing, etc. I've searched and read where the CDO.DLL needs to be the same as on my Exchange 2003 server. I searched my BES server and found many CDO.DLL files. My question is where should that CDO.DLL file reside? I'm assuming I need to delete all of them and just copy the one that is being used on my Exchange 2003 server, right? Do I have to stop and restart services or something after copying the file? Thanks!

[jibi]

CDO.dll is only for calendar not contacts.

[cayzac]

Sorry jibi, I meant calendar. I should really proof my own posts! Thanks, so with that said, what is the best practice on cdo.dll files (location, stop/restart services?).

Thanks again!

[jibi]

On the BES, install Exchange System Manager 2003 in the default location - C:\Program Files\Exchsrvr\. Once completed, upgrade to whatever Service Pack (1 or 2). Once completed, take the CDO.dll file from C:\Program Files\Exchsrvr\bin and place it in C:\Windows\System32 (or C:\WINNT\System32). Once done, register the DLL file from a Run window with 'regsvr32 c:\windows\system32\cdo.dll'.

If you've already registered CDO.dll in the past, then unregister it first - 'regsvr32 /u c:\windows\system32\cdo.dll' (or wherver you registered it in the past) - and then re-register it using the command-line above.

You could restart services, or just as quickly reboot the machine. I'd recommend the latter, just to be safe (takes about the same amount of time and the users will be affected in either situation, although it likely won't be noticeable, depending on how many users you have).

Any updates done in the future to ESM2K3 will result in it updating both CDO.dll files. You do not want any other CDO.dll files or registrations at any other locations on the server. It belongs in two different places only, with one DLL registration.

[jmanford]

Originally Posted by jibi

On the BES, install Exchange System Manager 2003 in the default location - C:\Program Files\Exchsrvr\. Once completed, upgrade to whatever Service Pack (1 or 2). Once completed, take the CDO.dll file from C:\Program Files\Exchsrvr\bin and place it in C:\Windows\System32 (or C:\WINNT\System32). Once done, register the DLL file from a Run window with 'regsvr32 c:\windows\system32\cdo.dll'.

If your running server 2003 and Exchange 2003 tools, you don't have to do any of this. I tried it and it works, no problems with syncing calendar.

[jibi]

You are correct, but the purpose of placing it in the System32 folder is to satisfy the installation of BES. Otherwise, it chirps everytime you do anything, stating that CDO.DLL doesn't exist.

[cayzac]

What about the mapi32.dll file? Do I need to do something similar with that as well? Thanks for the great information!

[jibi]

should be at the same level as your ESM patched. it is found in the \bin and automatically updated in the system32 directory.

[Natrone]

Question though. Jibi, are you saying that in the 4.0 environment you need the cdo.dll in two places? I'm pretty sure you are wrong here. It does not need to be in the system32 directory. Check the manual.

[Burgerking]

Putting the version of cdo.dll in the C:\Program Files\Exchsrvr\ and C:\Windows\System32 folders allowed me to run the BES 4.0 Installer without any errors. Prior to this I would always get the warning about cdo.dll.

Perhaps I missed an update or something during the setup of exchange?

Burgerking

[BBTechGuy]

The CDO file does not need to be in both system32 and the \bin directory. The only problem with it being in system32 is the Warning during the Installer however that won't impact your BES provided the CDO is registered correctly.

[jibi]

Originally Posted by Natrone

Question though. Jibi, are you saying that in the 4.0 environment you need the cdo.dll in two places? I'm pretty sure you are wrong here. It does not need to be in the system32 directory. Check the manual.

See BBTechGuy's statement. You are 100% correct that it states in the manuals that it doesn't need to be in both places, but RIM doesn't seem to want to correct the installer warning it gives during install. I also have had issues with installing ESM onto another partition/drive, although I'm not quite sure why they want to 'require' the default installation path. RIM suggested installing it in the default location to ensure there are no functional issues.

[cayzac]

OK, just noticed something else....I installed this BES server while we were still on Exchange 2000. I have the Exchange 2000 ESM installed. Since that time we have upgraded our Exchange Server to 2003 but I never went back and installed ESM 2003 on my BES. Its been working fine, with a few exceptions. Maybe I've just been lucky?? Anyway, should I just install ESM 2003 now on my BES? Should I uninstall anything? Stop any services? Or should I just let it install over top of ESM 2000?