03-29-2013 07:50 PM
One server we support is running BES Express on SBS2011 and all was fine until somebody installed Outlook on it. THis immediately caused a MAPI conflict which stopped the BES working.
I have uninstalled Outlook, uninstalled the MAPI and CDO, rebooted, deleted the MAPI profile in the registry, reinstalled the MAPI and CDO, but it still isn't picked up when I try and edit the MAPI profile in the BES Config tool.
I have run Windows Update on the server, upgraded Exchange to the latest SP3 and am now trying to upgrade the BES Express to 5.0.4 to see if these steps will recreate the correct MAPI links, but during the BES Express upgrade process it is still unable to connect to the MAPI, and in the pre-install it couldn't find cdo.dll (I can see it in C:\Program Files (x86)\ExchangeMapi, but can't register it - it comes up with the error "The module "C:\Program Files (x86)\ExchangeMapi\cdo.dll" failed to load".
I am at a loss as to what to try next - does anyone have any ideas about how I can get the MAPI installed correctly? I have tried plenty of reboots and reinstalls of the MAPI and CDO - there seems to be something not registered or pointing correctly but I can't see where.
03-30-2013 01:33 PM
I'm rockin the BlackBerry Passport, Z30, Z10, Q10, BlackBerry Mini Stereo Speaker, 64 gig PlayBook, BlackBerry Wireless Headset HS-700
04-01-2013 10:18 AM
glad to hea you are doing better, outlook on BES can break things fast
BESAdmin's, please make a signature with your BES environment info.
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V