Problems Getting MAPI CDO 1.1.2 Installer Package to Install

[philodendrin]

Our office recently migrated from Exchange 2003 to Excange 2007. We previously had BES Pro 4.x running on a standalone Win 2003 server. In order to get BES working on the Win 2003 box with Exchange 2007 (SBS 2008) I uninstalled the Exchange 2003 Management tools from the Win 2003 server and also uninstalled BES Pro 4.x in preparation for a new BES Express 5 installation.

Following the installation guide I attempted to install the Microsoft Exchange CDO MAPI 1.1.2 package. The CDO MAPI 1.1.2 installer says it installed successfully, but I can tell that it's actually doing nothing both by how fast the install screens go by and also because there's never a MAPI or CDO file actually placed anywhere on the server (nothing in C:\windows\System32 or anywhere else on C). There's also nothing listed under add/remove programs.

As expected, when I step through the BES Express installer it complains that there are no CDO files registered and can't verify any MAPI profiles.

I spoke with BB support and they had me delete any instances of CDO.DLL, EMSABP32.DLL, EMSMDB32.DLL, EMSUI32.DLL, EMSUIX32.DLL, GAPI32.DLL, MAPISP32.EXE, MSPST32.DLL, and WMSUI32.DLL ...as well as run the fixmapi.exe and fixmapisvc.exe utilities. After that I tried to install the CDO MAPI 1.1.2 package again... and again same results... the screens fly by but nothing actually installs.

I tried all of the troubleshooting steps logged on as BESADMIN and also as Administrator on the server... same results both times.

I can't complete the installation until the CDO and MAPI files are present and I'd rather not have to install BES Express on the SBS 2008 box, since I have a perfectly good Server 2003 box.

BB Support wants me to call Microsoft to have them figure out why their MAPI/CDO package won't install, but of course, MS wants $285 to help with the issue.

Anyone have any ideas here?

[Cellular Girl]

Sounds like none of your blackberry's are currently working if I read the above right. In that case, wipe the hard drive of the Windows Server 2003 and start from scratch. BES is finicky and your first paragraph above has my hairs on end.

Also check your subnets...don't now why but sometimes that's the issue. make sure Exhchange and BES are in the same subnet.

[engin]

There is a Windows Server patch that affects MAPI instqllation.

Check for KB981852 and if installed, uninstall and try again with the CDO install

[saukrateaz]

Wow, cellular girl wants to jump the gun. There is no reason to wipe and reload anything. Make sure you have the correct MAPI files. Uninstall Exchange manager from the BES (you will need to have an Exchange 2003 disk in the BES), reboot the BES and redo the mapi steps the BB tech had you go through. I just went through this a month ago. I was fed up, until I realized the Exchange manager had not been uninstalled from the BES. Exchange manager for 2003 is no longer needed on the BES.