Link to home
Start Free TrialLog in
Avatar of DigiSec
DigiSec

asked on

No calendar sync Blackberry Enterprise Server Express 5.0.2, Exchange 2010

I have a new installation of BES Express 5.0.2 with Exchange 2010 - They do live on the same server, using CDO 1.2.1 and Outlook 2010 (32bit)

I did a user/device data wipe for each phone as I provisioned it, and everything seems to work *except* the calendar.  I found the article here regarding the throttling policy and followed it to a 'T'

When I look at a user account, it shows "Wireless Calendar: Disabled" and in the MAGT logs I see "calendar=0" for everyone.  If I manually set a device to Wirless Calendar Sync on the DEVICE side - it gets changed BACK to disabled.

I've checked the Default IT Policy, and cannot find a specific setting for Wireless calendar, only for "Disable all wireless sync" which I set to "No"

I've resent service books, I've tried to manually sync the calendar from the BESAdmin - I'm at a loss now.

Thanks for your help.
Avatar of Rob Knight
Rob Knight
Flag of United Kingdom of Great Britain and Northern Ireland image

Hi,

You may need to force BES to use MAPI rather than. EWS?

Regards,


RobMobility.
ASKER CERTIFIED SOLUTION
Avatar of Mike Sullivan
Mike Sullivan
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of DigiSec
DigiSec

ASKER

Thanks for the ideas!  I'm heading to the client now.  I found this article on the RIM forums late last night and it matches my problem exactly.

http://www.blackberry.com/btsc/microsites/search.do?cmd=displayKC&docType=kc&externalId=KB19416&sliceId=1&docTypeID=DT_SUPPORTISSUE_1_1&dialogID=280232943&stateId=0

I'm going to try that first, and will try the MAPI suggestion above if it doesn't work out.  (This is now a production server, if I can fix it without multiple reboots in the middle of the day that's ideal.)

Avatar of DigiSec

ASKER

Ok - I tried the RIM KB article resetting the Calendars device side - no change.  I've gone through your process above to remove mapi32.dll and reinstall via MAPI CDO 1.2.1.... now the Blackberry Mailstore service won't start.

I no longer have a mapi32.dll located in c:\windows\system32\ - and I think that's the problem.

Can I open the MSI and extract the DLL dropping it in %\systemroot%\system32?

If you have installed the Mapi CDO tools then you should have a copy of it somewhere. Find it and drop a copy in System32. If not, reinstall the MAPI CDO tools.
Avatar of DigiSec

ASKER

Ok...can't find it.

To be clear, I'm installing the Exchange MAPI client CDO tools from here:
http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=e17e7f31-079a-43a9-bff2-0a110307611e

I've found the output path - no mapi32.dll....

I did a force re-install of that package (msiexec /fa <msi path>) from an administrative console - still no mapi32.dll

do I have the wrong package?
Avatar of DigiSec

ASKER

On a whim, I ran the Blackberry Server Configuration tool.  On the BlackBerry Server tab I clicked "Edit MAPI Profile".

The error is: "The MAPI system cannot be correctly initialized and used.  Make sure MAPI is installed and configured properly"

To reiterate, this is Server 2008 R2 x64 with Exchange 2010.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of DigiSec

ASKER

I'm awarding partial points to MikeTheRelic - his answer was right for Server 2003, but not for 2008 R2 (my version stated in the question).  And wasn't really anything different than what I had already found through Google.

I chased down RIM and Paid for a Microsoft Support incident to get the full answer
Thanks for the update DigiSec. I didn't see any original reference to Server 2008 but I should have guessed that you were using it as you were using Exchange 2010.
Avatar of DigiSec

ASKER

I'm awarding partial points to MikeTheRelic - his answer was right for Server 2003, but not for 2008 R2 (my version stated in the question)

I chased down RIM and Paid for a Microsoft Support incident to get the full answer