[Danny_Larouche]

As per documentation, MAPI32.dll and CDO.dll version should match, but it doesnt. Running exchange2000 and Outlook2002(XP) they should be using CDO version 6.0.5770.16 (as shown in admin manual). Whenever i try to download the correct file, i still receive the version 6.0.6487.2(SP4). Finally, the running MAPI32.dll version is 6.0.6249.0(SP3) and doesnt match either CDO version!!!!

Any idea?

[Danny_Larouche]

Hello!!!! Nobody is using exchange2000 with BES?

[CanuckBB]

It's not that MAPI and CDO need to match each other. It's MAPI on the BES matches MAPI on Exchange and CDO on the BES matches CDO on Exchange.

[stevebb]

It's the cdo.dll and mapi32.dll on the Exchange servers that needs to match the BES... We've always tried to keep them in sync (which is a problem for us as they patch/hotfix our Exchange servers quote often).

We rarely have problems when they are out of sync (have seen 2 cdo/calendar isues), but we always try to keep them in sync just to be safe.

Steve

[Danny_Larouche]

I have thoses files located in c:\WINNT\system32 and in d:\exchsrvr\bin

But none of them in the c:\program files\researchinmotion\Blackberryserver

[Danny_Larouche]

The MAPI32.dll seem correctly loaded in modules

However, CDO.dll is not shown in system "loaded modules". Is it normal?

[morser]

Hmm, what if i have installed System management tools for 2003 on the BES because we are moving to exch2003 this year, but currently are on Exch2000. Is it ok to copy the exch2000 cdo.dll and mapi32.dll files to my BES server with exch2k3 system management? I'll try.

So many issues with CDO. almost worth having a service or program running on BES to keep things in order with this. Imagine a service on bes that is given permission to check versions and perform what's necessary to keep them in sync. I'm always up for easy solutions to problems that affect SO many admins. So many CDO posts...

[slimbim]

I talked to T-support last night about this, and I was told that the versions do not have to match exactly, but just have to be same or higher.

So the versions of CDO.dll and Mapi32.dll on the BES server just needs to be same or higher version than the ones installed on the exchange servers.

I haven't tested it yet though. Doing it this weekend. Installing BES 4.1 on Win2003 that will talk to Exchange 5.5 on Win2000.

[morser]

Slimbim,
How did the installation go?

[slimbim]

I did not have any issues adding and wirelessly activating against mailbox on Exchange 5.5.

BES is BES 4.1 on Windows 2003 with Exchange 2003 admin tools (including 5.5) and Exchange SP2. Exchange is 5.5, and don't have too much details as I don't manage these exchange servers, but it being 5.5, I'm sure the cdo.dll and mapi32.dll on them are of lower versions than what is on BES.

I did test message receive and send from device with no issues. I haven't had chance to test calendar sync, but as long as your BES Admin mailbox is on the 5.5 org the users are on I think it is ok. as this is in a test environment, for MDS app develpment/test i did not test every single functionality.

[|||||||]

Originally Posted by slimbim

I talked to T-support last night about this, and I was told that the versions do not have to match exactly, but just have to be same or higher.

So the versions of CDO.dll and Mapi32.dll on the BES server just needs to be same or higher version than the ones installed on the exchange servers.
.

That's correct the same or higher. Since you can't put ESM 2000 on windows 2003 server.

[T-Roy]

For others running Exchange 2000 and do not have access to Exchange 2003, the best bet is MAPI/CDO 6.0.6603.

You install this by applying Service Pack 3, and then the Post Sp3 August 2004 rollup.