Hi all-
I've been racking my brain the past week trying to resolve a one-way sync issue with our BES and Exchange 2007 SP3.
When calendar events are created on a device, they don't sync back to Exchange, and the following entries show up in the MAGT logs:

[40000] (02/15 09:02:44.656):{0x1388} [BIPP] Received datagram, Tag=4401838
[40700] (02/15 09:02:44.657):{0x157C} {<user email>} Receiving packet from device, size=85, TransactionId=1115691827, Tag=4401838, content type=CICAL, cmd=0x3
[40000] (02/15 09:02:44.657):{0x157C} {<user email>}-HandleAppointmentToSynchronize-Entering-Tag=4401838
[30193] (02/15 09:02:44.657):{0x157C} {<user email>} Receiving calendar update from device, RefId=16943929, Tag=4401838, TransactionId=1115691827
[40000] (02/15 09:02:44.658):{0x157C} CDO helper 01ABE538 is not in memory
[40000] (02/15 09:02:44.658):{0x157C} Starting new CDO helper 01ABE538
[40574] (02/15 09:02:44.838):{0x2060} CDO helper 01ABE538 started, PID 7292
[40000] (02/15 09:02:44.895):{0x157C} {<user email>} StartCalHelper - CDO profile created BES_CDO_8448_326
[30001] (02/15 09:02:45.844):{0x2060} CDOCalendar::Initialize - Code = 80040705, WCode = 0505, Code meaning = IDispatch error #1285,
[30002] (02/15 09:02:45.844):{0x2060} Server = <email server>, Mailbox = <exchange DN for user> Description = The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. [Microsoft Exchange Server Information Store - [MAPI_E_FAILONEPROVIDER(8004011D)]]
[30180] (02/15 09:02:45.844):{0x2060} {<username>} CDOCalendar::Initialize - Error in call m_spCalendarFolder = m_spCDOSession->GetDefaultFolder

All of the other sync items (mail, contacts, etc) are working fine, and calendar syncing from Exchange to the device works as well. I've gone through the calendar troubleshooting steps from RIM, and still can't resolve it. Our BESadmin account has all the necessary permissions.

Previously, we were at 5.0.1 with MAPI/CDO 1.2.1 version 6.5.8131. Last night, I updated to 5.0.2 MR3 with MAPI/CDO 1.2.1 version 6.5.8190. RIM's BES support matrix says that 5.0.2 is recommended to use MAPI/CDO 6.5.8165, but I have been unable to find it anywhere (only 8190).

Any suggestions are greatly appreciated!


Thanks!

8165 was replace by 8190 a whi8le ago. I have a copy of it if you really think it is needed.

__________________
------------------------------------------------------

Torch 9800 on BES 4.1.6 MR7, Exchange 2003, SQL 2005.
WES 2009-2010 Survivor

I was just thinking about using it as a point to troubleshoot, since RIM doesn't say 8190 is supported in their matrix. I'm just curious if anyone else with Exchange 2007 SP3 is using the same version of CDO.

Looking in the CALH logs, I found the following:

[30000] (02/15 07:29:30.005):{0x210C} {<user email>} Service::TestAccessToMailbox Soap Exception caught: The server to which the application is connected cannot impersonate the requested user due to insufficient permission.
[30000] (02/15 07:29:30.005):{0x210C} {<user email>} Diagnosis: The BES service account does not have impersonation rights on the CAS server.
[30000] (02/15 07:29:30.005):{0x210C} {<user email>} Please consult the BES installation guide for Exchange Server configuration information.

I found a great article here with this as a suggestion:

To enable impersonation rights across all the Microsoft CAS, use the following command in the Exchange Management Shell:

get-clientaccessserver | add-adpermission -User <BESadmin> -ExtendedRights ms-Exch-EPI-Impersonation

Once I added the impersonation rights to the BES account and restarted the BES agents, calendar syncing was fixed.


Lesson learned: check ALL of the logs...

i was investigating the same here but all calendar syncs are working . did you have to do this?
KB20157-How to enable BlackBerry Enterprise Server 5.0 SP1 and SP2 to use Microsoft Exchange Web Services

i dont understand when you would have to do this kb compared to just giving Impersonation

Ya that KB is a little over kill.. you really have to rive it a once over to see what's needed in your org. I did'nt do any of the optional steps as they typically tie your BES to a single server (e.g. cas server) and that's bad for fault tolerance,etc...

In my setup (Exchange 2007 SP3) I only did the following steps and all works with no issues:
Tasks 1,3 (not needed as my BES ADMIN is a memember of a group that grants perms on all exchange CAS).

Task 4 you can skip if you're not using a Self signed cert (I.E. Externall CA like digicert,verisign,etc..)

Task 5 you can skip if you're running SP2 on BES 5

Task 6-8 I skipped as they tie you to a specific resouce

Task 9 need to do

Hope this helps.

Z