[david_glover]

Ok guys,

I could use your help with something…I’ve got two servers, both running Small Business Server 2000. Server 1 is running the Exchange Server and Server 2 is running BES 4.0. A “specialist” installed BES but didn’t know about the CDO and MAPI file issues, and now I’m left trying to fix the Calendar Bi-Directional Synchronization issues. Here's what I've got so far:

1. I copied the cdo.dll file from Server 1 to Server 2 so they are now the same versions. I registered the file using regsvr32. When I try to install Service Pack 2 for BES 4.0, it says “Unable to load cdo.dll - calendar functionality will be disabled.” That’s one issue, but I think it may be related to the following...

2. Server 2 does not have Exchange installed on it, just Server 1. I’ve read that the Service Packs for Exchange have to be installed on both machines, but I can’t install the Exchange Service Pack on Server 2…what do I do?

3. Where do I install the cdo hotfix on Server 2 since I don’t have Exchange on Server 2? Do I only install it on Server 1? Also, I have users using Outlook 2003 and XP...what hotfix version do I use?

4. I copied the mapi32.dll file from Server 1 to Server 2 but that generated the "unable to connect to database" error…I put the old mapi32.dll file back on Server 2 and the database error message went away. How do I get the same mapi32.dll version on both machines?

Should I un-install BES 4.0, get the CDO & MAPI file versions the same, then reinstall BES?

Or…

Is there a way to update the MAPI and CDO files without uninstalling BES and without generating database errors?

Or...

Should I un-install BES from Server 2 and re-install it on Server 1? Server 1 isn't the fastest thing ever made and I know most people don't recommend it!


Thanks in advance!

[greywolfe]

I'm gathering you have Exchange 2000 SBS? The latest cdo version that is available for 2000 should be 6.0.6487, which is available from http://www.microsoft.com/downloads/d...displaylang=en

What I would do is set the BES services to manual and shut down your bes server. Then apply this cdo patch to the exchange server and reboot it. bring up the bes server again and copy the cdo.dll from the exchange server to the location you've installed exchange system manger, usually exchsrver/binn (this is a requirement for sp2) and register it. Then attempt to apply sp2 for BES 4.

[david_glover]

Let me add a few more details about the servers:

Server1 is the Exchange Server
Server2 is the BES Server

Server 1: cdo version 6.0.6487.2 (exchsrvr\bin)
Server 1: mapi version 6.0.6487.1 (exchsrvr\bin)

Server 2: cdo version 6.0.6487.2 (winnt\system32)
Server 2: mapi version 1.0.2536 (winnt\system32)

Greywolfe, you said to copy the cdo.dll from the exchange server (Server1) to wherever exchange system manager is installed (exchsrvr\bin)...BUT, I don't have Exchange installed on the BES server (Server2)...i.e. no exchsrvr/bin location.

Do I just create the directories in Windows, or do I need to install something on Server 2?

What about the Mapi version conflict?

[jibi]

My guess is that he doesn't have ESM installed. He says he can't install the Exchange SP because Exchange isn't installed on it.

So, make sure that ESM 2000 is installed on Server 2 and patched to the same level as Exchange is on Server 1. The CDO.dll file most likely won't be installed with ESM on 2000, so copy it to C:\Program Files\Exchsrvr\bin on Server 2 and register it (you can do this prior to patching and the Service Packs will update CDO.dll as you go along).

I don't like applying the CDO hotfixes simply because I'm not going to install them in an Exchange environment that has no issues with calendaring anyhow. If the Exchange environment requires those patches, then do them on the BES servers. If you have no issues in the Exchange environment, then don't patch the BES with anything more than the current patches/service packs found on the Exchange servers.

Also, make sure that you don't have Outlook installed in place of Exchange System Manager on Server 2. You may want to look through the Installation Guide - honestly, its very easy to install the BES server and get it working.

[david_glover]

Gotcha...after I had posted the first reply I started searching for ESM...now we're getting somewhere.

Thanks!

[BBTechGuy]

Originally Posted by jibi

Also, make sure that you don't have Outlook installed in place of Exchange System Manager on Server 2. You may want to look through the Installation Guide - honestly, its very easy to install the BES server and get it working.

mapi version 1.0 would point to Outlook as you said jibi. That version comes with Outlook as opposed to ESM. Correct that by uninstalling Outlook and then installing ESM with appropriate patches.

Your description of "Calendar Bi-Directional Synchronization issues" tells me that you should spend less time on CDO and more on verifying that your Exchange Permissions match those specified in the Guide exactly. Too many permissions/group membership isn't always a good thing. For example, the BESAdmin being a Domain Admin is not good.

[greywolfe]

Yeah defiantely looks like no Exchange admin tools installed...as the others have said, its a basic preinstall requirement. Frankly Im surprised it didn't throw a hissy fit during the install.

Make sure Outlook is NOT installed on the BES (uninstall if it is) and install ESM.

Jibi: The only time we'd recommend CDO hotfixes are if the current version on the Exchange server is not up to the version recommended for your Exchange/Outlook combination. The problem is that this is a preinstall requirement that most often than not is *not* completed before the install of the BES. If the install guides were read correctly (and I know they can be vague sometimes) then these CDO fix issues would not come up. Pretty much *every* cdo problem that I deal with arises from this fairly simple preinstall requirement not being completed.

[jibi]

Originally Posted by greywolfe

If the install guides were read correctly

hehe. i just had to quote that one... very sound advice (just too bad no one seems to really think about doing it)