If anyone can figure out this problem you will find yourself far more superior with adminstering BES then RIM themselves. I just spent 4 hours on the phone with RIM and pretty got "you're on your own now" as my answer.

I have BES 3.6 SP3a with Hotfix 2 and an Exchange 2000 infrastructure. Just two weeks ago my users started notifying me that their wireless calendar sync stopped working. I checked all the obvious such as services, made sure the mapi profiles were working properly and the besadmin user had access into their mailbox.

I also checked to make sure that I have Exchange 2000 SP3 installed on both the Exchange server and the BES server. Also I have checked the versions of CDO.DLL and MAPI32.DLL and they are the same on both servers.

CDO.DLL Version: 6.0.6249.0
MAPI32.DLL Version: 6.0.6249.0

If anyone has any suggestions on how to fix this problem that would be great.

send an invitation to the user. they should at least get the meeting invite. Open the meeting invite and check to see if they can accept. if the calendar functionality is not present on the device.. then they are no longer wireless users. you might want to togle them from wireless to regular synch and back to wireless.

I would agree...but if its a global issue, let us know...whole different ballgame then.

alright, I'll let you know. I probably won't be able to get to this users laptop and blackberry until tomorrow.

Which way works and which way is broken? Does Outlook-->HH work? Does HH-->Outlook work?

Upgrade the CDO.DLL on your BlackBerry server to version 6.0.6487.2 ... if your users that are having a problem are running Outlook 2003 ... you need at minimum, the CDO version I indicated above in order for wireless calendar synch to work as designed.

Microsoft introduced a new calendar attribute with Outlook 2003 and the old CDO doesnt know how to read the attribute ... thus causing wirless calendar synch to choke with users on Outlook 2003.

This should solve your problem, and no, you do not need to apply this to all of your Exchange servers ... just the BlackBerry server will be enough to solve the issue, if indeed it is Outlook 2003 users that are having the problem .... if your Outlook 2000 users are having the issue ... then time to beat up RIM support some more

not sure if this will help at all.

I had a user that was only able to sync one way... I spent hours on the phone with rim doing everything from removing and reinstalling service book entries to completly removing the user and rebuilding the handheld.

turns out they just had a crap load of appointments. i changed them back to outlooksync ---> told it to only sync future items -----> and then changed them back to blackberry wireless sync and it started working fine.

If the situation is just that syncing occurs only one way, then reset the devices.

Anyone get this problem figured out yet? dshearon I tried that method you last mentioned, I still can't get the 7250 to sync up to outlook calendar. It will work for everything else tho ( ie; email, tasks, memos ).

Had similar problem. In Exchange had to configure Blackberry service account so it had enough permissions to access and modify a user's mailbox.

I've been having this problem with our company server (SBS/Exchange 2003), Outlook 2003, BES Small Business, etc.

The Outlook calendar syncs to the BB fine, but not vice versa. I tried copying CDO files and checking permissions, but I don't see a BESAdmin in Active Directory. I suspect this is due to it being the Small Business BES. If so, what user should have rights and where?

I am having the same issue on SBS 2003 / Exchange
It will sync from exchange/outlook to blackberry but not the other way.

Please help.

My problem ended up being not having the proper user set up. In the end I ended up resintalling BES after setting up the proper account on the server (BESAdmin). A little annoying, but not overly complicated. Docs are on the RIM site.

Simplest way to resolve this one-way Wireless Calendar sync failure from BB to Outlook is to install the latest Service Pack on the BES under the correct BES Admin service account. This will cause all the services to run under the correct account after the SP upgrade has been applied and the wireless calendar will then sync in both directions. Easy!!