
08-25-2009, 09:29 PM
|
 |
Proprietor
|
|
Join Date: Nov 2008
Posts: 2,238
|
|
KB14075 - Calendar synchronization does not work from BlackBerry to Outlook
KB14075 - Calendar synchronization does not work from the BlackBerry smartphone to Microsoft Outlook
Environment
- BlackBerry® Enterprise Server for Microsoft® Exchange
- Microsoft Hosted Messaging and Collaboration (HMC) 4.0
- Microsoft Provisioning Service (MPS)
Overview
One way calendar synchronization is not working from the BlackBerry smartphone to Microsoft® Outlook®
The following log lines are displayed:
[30001] (08/14 13:58:46.822):{0x164C} CDOCalendar::Initialize - Code = 80040705, WCode = 0505, Code meaning = IDispatch error #1285,
[30002] (08/14 13:58:46.822):{0x164C} Server = exchange, Mailbox = /o=My Organization/ou=First Administrative Group/cn=Recipients/cn=user Description = The attempt to log on to the Microsoft Exchange Server computer has failed. [Microsoft Exchange Server Information Store - [MAPI_E_FAILONEPROVIDER(8004011D)]]
[30180] (08/14 13:58:46.822):{0x164C} {user} CDOCalendar::Initialize - Error in call m_spCalendarFolder = m_spCDOSession->GetDefaultFolder
[40000] (08/14 13:58:51.028):{0x164C} CDO initializing failure in CDO helper 00f31e78 (5)
[40580] (08/14 13:58:52.029):{0x164C} CDO helper 00f31e78 closing after CDO initialize failure
[40000] (08/14 13:58:52.129):{0x164C} CalHelper failed 00f31e78, ErrorCode = -11, Thread activity was Checking CDO object list
The following error message is displayed when you attempt to connect to the affected BlackBerry smartphone user's Microsoft Outlook mailbox using a profile that does not have cached Exchange mode turned on:
The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
Cause
This issue has multiple causes.
- The public folder store is not mounted.
- The BlackBerry Enterprise Server service account does not have the appropriate permissions.
- The protocolSettings in the Microsoft® Active Directory® is configured to deny MAPI connections.
Resolution
Complete the appropriate resolution for the cause of the issue.
Cause 1
The public folder store is not mounted.
Resolution 1
Make sure the public folder store is mounted.
Cause 2
The BlackBerry Enterprise Server service account does not have the appropriate permissions.
Resolution 2
Verify that the BlackBerry Enterprise Server service account has the same permissions as the mailbox store.
Cause 3
The protocolSettings in the Microsoft Active Directory is configured to deny MAPI connections.
For more information about this cause visit Microsoft TechNet: Resources for IT Professionals and search for article Exchange 2003 SP2 Disabling Mapi/Non-Cached Access Per User. Resolution 3
Microsoft Exchange 2003 SP2 and Microsoft Exchange 2007 SP1
Complete the following steps:
- Install the Windows 2003 Support Tools if the tools are not currently installed.
- Open adsiedit.msc.
- Expand Domain [servername.domain.com] and then the respective container that contains the user object for the protocolSettings that you want to check.
- Right-click the desired user and select Properties on the context menu.
- Select protocolSettings from the list of properties and click Edit.
- If the values MAPI§0§0§§§§§§ or MAPI§1§1§§§§§§ exist, then MAPI access has been turned off for this user. Remove the value. Note: It may take 15 minutes to 2 hours for this change to take effect.
Note: By default when the Multi-valued string is blank, no value is defined and MAPI access is allowed.
HMC 4.0 and later
If the MPS was used to create the user accounts and mailboxes in a hosted environment, the configuration settings of the front-end application that was used to create the accounts must be changed. The change to the configuration settings makes the required changes to all user accounts that were created using MPS.
__________________
http://blog.port3101.org/hdawg/
The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.
|