BlackBerry Forums Support Community               

Closed Thread
LinkBack Thread Tools
Old 04-08-2008, 10:01 AM   #1 (permalink)
New Member
Join Date: Apr 2008
Model: 7100T
Carrier: BES
Posts: 1
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Bi-Directional Calendar Sync not working

Please Login to Remove!

We have a BES 4.0 server running on a DC, and a Exchange 2003 SP2 server (both a VM's). Some users are unable sync calendar items in both directions (they can sync from outlook to BB, but not BB to Outlook)

I have checked Exchange delegation and permissions, I am positive that the bes service account has the right permissions and is not being denied somewhere

I have checked cdo.dll and mapi32.dll on both servers and they have the same version (6.5.7651.61 for cdo)

I have tried pretty much everything I can think of, any help would be great.

Old 04-08-2008, 06:12 PM   #2 (permalink)
BlackBerry Extraordinaire
gibson_hg's Avatar
Join Date: Dec 2007
Model: NA
PIN: 80081ES
Carrier: NA
Posts: 1,006
Post Thanks: 0
Thanked 0 Times in 0 Posts

Try this:

1. Pick a user and enter an appointment on their BB
2. Look in the MAGT log for that users email address around the time you tried the appointment
3. Look for a line with CDO

That line will tell you what the issue is. This issue is always permissions or CDO, seeing as CDO seems ok then it's permissions. If you are positive they are set correctly then the account itself is the issue.

When you create an appointment in Outlook it reaches the BB like an email. When you create an appointment on the BB the account needs permissions to access the mailbox and create the appointment there as well.

Keep this in mind: The BES is on a DC. Is the BESAdmin in any admin groups other than built-in admins? This is the only admin group the BESAdmin can be in and it only works when the BES is on a DC.

Have you reviewed this article? BlackBerry Search Results

Copy and paste the log lines here if you want, they will tell you exactly what is going on.
Old 04-09-2008, 11:31 AM   #3 (permalink)
Thumbs Must Hurt
Join Date: Jan 2005
Model: 9700
Carrier: T-Mobile
Posts: 95
Post Thanks: 0
Thanked 0 Times in 0 Posts

I had the exact same issue two days ago. It was a memory leak issue caused by a corrupt registry entry. Rim support walked me through it and the issue was resolved.
Old 04-09-2008, 02:51 PM   #4 (permalink)
New Member
Join Date: Apr 2008
Model: 8100
Carrier: att
Posts: 14
Post Thanks: 0
Thanked 0 Times in 0 Posts

Looks like a Memory leak problem. Take a look at this
BlackBerry Search Results


Copyright 2004-2016
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.