Originally Posted by Crowdie
MAPI is a UDP based protocol for communicating with Microsoft Exchange. The BlackBerry solutions for Microsoft Exchange use the MAPI protocol to communicate with Microsoft Exchange.
You must install the Exchange System Manager onto your BES for Exchange server for two reasons:
1. It is required to complete the pre-installation tasks (granting of permissions)
2. You have to open and close the Exchange System Manager on your BES for Exchange server to initialise the MAPI subsystem on that server. If you don't when you go to start the BES you will get MAPI errors (always starting with a "8")
You will also get a MAPI error if you have just created a System Account, normally BESAdmin, and given it a mailbox and don't send it an E-mail BEFORE starting the BES server.
If you do not have an Exchange CD, to install the Exchange System Manager from, I suspect you shouldn't have an Exchange server.
If you get a "module not found" error when you attempt to register the CDO.DLL then copy the CDO.DLL to the \Windows\system32 or \WINNT\system32 (whichever applies to your server) and then type "regsvr32 cdo.dll".
Operating System: Windows 2003 Terminal Server Service Pack 2
No Previous Installation of BlackBerry Components found.
Prerequisite Components Installation Information:
Java version 1.5.0_09 detected.
Microsoft XML 4.20.9818.0 detected.
Microsoft .Net version 1.1 detected.
WARNING: Unable to find Collaboration Data Objects library (CDO.dll).
WARNING: Exchange Server is not detected. A newer version of mapi32.dll may need to be installed.
WARNING: If you are using SNMP monitoring, you must install the SNMP service before you install the BlackBerry Enterprise Server.
So I get this. I just did a complete reinstall of the ESM for 2007 (we're an Exchange 2007 native org).
MAPI32.dll is present on both servers (Exchange and BES) and versions match (1.0.2536.0).
I've tried manually registering it, but I get a no entry point error message.
I do not have CDO.DLL on any server in my Enterprise, nor is it on the MSDN media. I *do* have an excdo.dll file in the Exchange setup folder. Environment
Windows 2003 Native Mode Active Directory on Sun and Dell hardware over Cisco switches.
Windows 2003 SP2 x64 on dual Athlon boxes.
Can anyone advise, or should I just call RIM?