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.
DigiSecAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rob KnightConsultantCommented:
Hi,

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

Regards,


RobMobility.
0
Mike SullivanDirectorCommented:
Hi DigiSec,

I think you will need to get rid of Outlook 2010 from the server to get BES Calendars to function properly. Historically, the MAPI tools that form part of the Outlook client differ to the MAPI tools required by BES.

Remove Microsoft Outlook and repair the Messaging Application Programming Interface (MAPI) subsystem by completing the following steps:

Stop the BlackBerry Enterprise Server services by completing the following steps:
Open the Control Panel.
Double-click Administrative Tools.
Double-click Services.
Double-click each BlackBerry Enterprise Server service and click Stop.
Set each service startup to Manual
Click Ok to close.

Remove Microsoft Outlook using Add or Remove Programs.
Search for and rename any MAPI32.DLL files with the file version of 1.0.2536.0 to MAPI32.OLD.
From the Add/Remove programs, remove the Microsoft Exchange System Tools or the MAPI and Collaboration Data Objects 1.2.1 if installed.
Restart the BlackBerry Enterprise Server.

Install either the Microsoft Exchange System Tools or the MAPI and Collaboration Data Objects 1.2.1.
If necessary, install any appropriate Microsoft Exchange or MAPI 1.2.1 service packs and updates on the computer hosting the BlackBerry Enterprise Server.
Restart the BlackBerry Enterprise Server.

Restart the BlackBerry Services:
Open the Control Panel.
Double-click Administrative Tools.
Double-click Services.
Double-click each BlackBerry Enterprise Server service and click Start.
Set each service startup to Automatic.
Click OK to close.

After the above steps are complete, the BlackBerry Messaging Agent logs will show the following:

[30000] (01/26 20:41):{0xF38} Current Date: 2010/01/26
[30000] (01/26 20:41):{0xEAC} [ENV] MAPI32.DLL: C:\WINDOWS\system32\MAPI32.dll, Version: 1.0.2536.0
[30000] (01/26 20:41):{0xEAC} [ENV] CDO.DLL: C:\Program Files\ExchangeMapi\cdo.dll, Version: 6.5.8131.0 (or higher)
[30000] (01/26 20:41):{0xEAC} [ENV] Loaded MAPI32.DLL: C:\WINDOWS\system32\MAPI32.dll, Version: 1.0.2536.0
[30000] (01/26 20:41):{0xEAC} [ENV] Loaded EXMAPI32.DLL: C:\Program Files\ExchangeMapi\exmapi32.dll, Version: 6.5.8147.0

Note: The MAPI32.DLL for Microsoft Outlook and the 1.2.1 CDO Client Package are different, but both have the same version number: 1.0.2536.0
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DigiSecAuthor Commented:
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.)

0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

DigiSecAuthor Commented:
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?

0
Mike SullivanDirectorCommented:
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.
0
DigiSecAuthor Commented:
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?
0
DigiSecAuthor Commented:
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.
0
DigiSecAuthor Commented:
Ok - Here's the *RIGHT* right answer (MikeTheRelic was mostly right, but it will cause you to spin in circles on 2008 R2 x64)

Stop and disable all Blackberry Services
Uninstall Outlook
Uninstall Previous version of MAPI CDO 1.2.1 reboot.
On 2008 R2 x64 DO NOT RENAME existing MAPI32.DLL files
Check C:\Windows\System32\ and verify that there is a MAPI32.DLL with Version 1.0.2536.0 (file date of 11/20/10 6:26 AM)
If it doesn't exist, run C:\windows\system32\fixmapi.exe as administrator and it will be created
Verify that the same file with the same version, file date and size also exists in c:\windows\syswow64\
Install Exchange MAPI CDO 1.2.1 as normal
Run the Blackberry Server Configuration tool as administrator and Edit the MAPI profile
Re-enable and restart Blackberry services etc as above.

MikeTheRelics answer is correct for Server 2003, however on 2008 R2 (which is x64) the Exchange MAPI CDO installer doesn't create a new mapi32.dll as expected, instead it uses the mapistub facility to create referential objects in the registry.  This is important since it is a 64 bit OS creating links to 32 bit DLLs for 32 bit software.  It can't properly create the references if the DLLs don't already exist in the path (they get referenced to c:\Program files (x86)\ExchangeMapi\EXMAPI32.DLL)  It took a 3 hour call to RIM where they tried Mikes answer about 10 times before punting it to Microsoft.  Another 3 hour call to Microsoft who traced each step of the install to find this one.

And yes, switching to this version of MAPI instead of the Outlook version fixed my calendaring issue as well.

0
DigiSecAuthor Commented:
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
0
Mike SullivanDirectorCommented:
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.
0
DigiSecAuthor Commented:
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
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
BlackBerry Programming

From novice to tech pro — start learning today.