Ok, i have narrowed down a calendar problem we are having.

our users (most of whom are on 7250's verizon) will add an item to their calendar on the blackberry. It will not show up in outlook. However, if they add an item onto their calendar in outlook it will synch to the blackberry.

We use BES 4.0.0.110. I am checking the mapi32.dll and cdo.dll as suggested in another post i found. However i believe they will match.

My 7100i works perfectly. So will any of the newer blackberries. Could this be a firmware issue? They have the option in calendar for wireless synch (set to yes).

Check wireless sync is set to yes on the devices and the BES, and check your CDO. With the CDO you need to make sure you have a CDO installed and registered on Exchnage and on the BES in Exchange BIN and System32 folders. All the CDO files must be the same version.

As a side note, are the affected users using a different version of Outlook to the working users???

BES 4.0.0.110??? put some service packs on that.

What groups is your besadmin account a member of?

I agree with TB. Check your log MAGT log file. Open it in notepad and search for IDispatch 1271. If you find it, you are having the same prob i did. To fix it, I upgraded to 4.0.5a and the hotfixes. Solved all my wows and some other small things that were happening. As of now, calendar sync is working as expected again.

Thanks again to TB for and some others here for their guidance.

Keith

Just a quick thought...
had a user w/caledar issues. He had changed calendar option on handheld to "Keep Appointments-" "forever".
I disbaled/re-enabled wireless synch, the "Keep Opointments" option defaulted to 30 days (I believe" and the caledar began synching... fixed his issue.
I assume 'forever' filled space....
I realize this seems too simplistic, but you never know...

you difinately need to upgrade SP, there are lots of issue to resolve this issue.

however form what you are saying it seems this works on one device therefore this maybe an issue with permissions.

didn;t catch your exchange version.

make sure its not a member of any groups within AD as it probabily has an explicit deny from group membership.

can you provide the following

exchange version and SP
group membership of the BESadmin account
MAPI and CDO version
how many exchange servers and whether the effected user is on a different exchange server from the person that works

from this, would have a good idea where the problem lies