[nick119]

Hey guys -

I recently started a new job as an IT guy at a company that's running a BES server. And recently, I've come across 2 users that have been having weird calendar syncing issues. For example there are clearly appointments on the users blackberry that are not in the users outlook calendar and vice versa. Although I have not been able to replicate the issue these users are experiencing (everything seems to be working fine when i put in test appointments both ways, it works fine), there are appointments in his calendar on his blackberry that are not showing up in outlook, as well as the other way around. I've tried hard resetting the device, and verified all settings were correct in the exchange manager. The weird thing about this is when I go in on the device that is showing the screwed up appointment and update it, it then syncs properly (only with that appointment however).

Has anyone else experienced this issue before?

This may be a little confusing, because it's hard to explain haha, but if you need any further clarification please let me know.

Thanks so much in advance.

Regards,
Nick

----------------------------------

Another thing I've seen that he has a lot of shortcuts and 3rd party applications installed (as it's his personal bb). I'm wondering if this could be causing the issue. The next step would be a complete device wipe, I just want to give it a little longer to resolve itself.

[gibson_hg]

We will need some info to correct this issue:

1. BES Version
2. Exchange Version
3. MAPI32.dll/CDO.dll versions on both the BES and Exchange
4. How many users are on the BES? How many affected? Could be more than the
2 you mentioned
5. Are these single appointments or a reoccurring appointments?

The CDO version is a key file here as it is responsible for wireless calendar. If the BES is lower than Exchange you will need to unregister the old one on the BES, remove it, copy/paste the newer one from Exchange, register it and restart the Dispatcher service.

Let us know what you find.

[nick119]

1. BES Version: 4.1.4.26
2. Exchange Version: 6.5.7638.1
3. Mapi32.dll (Exchange): 6.5.7638.1
Mapi32.dll (BES): 6.5.7638.1
CDO.dll (Exchange): 6.5.7651.61
CDO.dll (BES): 6.5.7651.61
4. There are 84 users currently on our BES. It possibly can be more than the 2 users i've mentioned, but these are the only two who have complained so far.
5. I've seen it happen with both types of appointments but it seems to be mostly with Single appointments.

Thanks for all your help.

[ashworth]

If you are not able to reproduce the issue and all of the other users on the BES are fine, I would ask the end users what they are doing that might cause this to happen. I had a case onces where I was talking to RIM and they provided me this URL: http://office.microsoft.com/en-us/he...276781033.aspx and after going though this I had a lot less Calendar related issues (both in Outlook and by my BES users) (This might make a good blog post)

[fadmin]

Search for these:
CDO.dll (BES), Mapi32.dll in C:\windows\system32 and see if the version is the same. If not make them the same.

[gibson_hg]

Search for these:
CDO.dll (BES), Mapi32.dll in C:\windows\system32 and see if the version is the same. If not make them the same.

This info was provided above, it was the users second post in this thread. Also, CDO and MAPI32 will not match in Exchange 2003 SP2 due to cdo.dll being higher for the DST change. MAPI32.dll will remain at 6.5.7638.1 and cdo.dll will be 6.5.7651.61.

So you're post to make them the same does not apply to Exchange 2003 SP2, other than that it is.

[MarkF]

Ashworth - Thanks for the link on Calendar issues, excellent stuff in there!