BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 10-07-2010, 05:12 PM   #1 (permalink)
New Member
 
Join Date: Aug 2010
Model: 8330
PIN: N/A
Carrier: verizon
Posts: 3
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Calendar issues

Please Login to Remove!

We have Exchange Server 2003 SP2 on a Windows 2003 Standard SP2 (physical box) and a Blackberry Exchange Server (BES) on W2K 2003 Standard SP2 (VM). BES version is 5.0.1.58 – We have about 70 users on the BES. All Outlook clients are 2007 on WinXP SP3 physical machines. All the problems have been with the same 5 or so users. All involved are using cached mode in their Outlook. Most of these user’s have delegates on their Calendar.

Generally speaking the problems have been as described below:

- User accepts an invitation in Outlook and the invitation goes straight into the deleted items folder but does not go into the calendar. By default the invite should go into the deleted items folder since action was taken on it, but it should obviously go on the calendar as well.
-User accepts a meeting on their blackberry device, but they get an error basically saying that the invite or email couldn’t be found since it may have already been modified. I know this may have to do with the time difference between when the mail arrives on the Outlook client and the BB device and if it’s modified on one, the header (stamp information) is changed and that’s why there may be communication errors.
- User sends out an invitation to multiple users, then user sends out an update to all the users, only some receive the update.
- User sends out an invitation to multiple users, an invitee requests a “propose new time request” and the originator accepts the proposed new time and either some users aren’t notified or the requestor becomes the organizer and half the attendees are missing.
- User A receives an unintentional invite from user B on behalf of user C, and on user B sent items or deleted items there is no record of them sending this invite.

From the issues described above there is one user, the COO, who seems to be the one affected the most. His BB device has been wiped a few times, his account on the BES has been deleted and recreated. He has had a new laptop (New Outlook Profile) and problems still remain.

On recommendation of Blackberry (RIM), we created a registry key on the BES server that delays emails for a few seconds coming from the BES to the BB device, since BB users were getting their emails before it was received on their Outlook from Exchange and if the email was modified on the BB and not yet received on the Outlook client sometimes errors would occur.

blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB00 139]KB00139-How to delay email processing to allow email messages to be scanned by antivirus or anti-spam software before being delivered to the BlackBerry smartphone[/url]

Does anyone have any recommendations that may help?

Thanks!
Offline  
Old 10-07-2010, 07:34 PM   #2 (permalink)
BlackBerry Extraordinaire
 
CanuckBB's Avatar
 
Join Date: Feb 2006
Location: YYZ
Model: 9900
Carrier: Rogers
Posts: 1,183
Post Thanks: 0
Thanked 2 Times in 2 Posts
Default

Quote:
Originally Posted by tolinrome View Post
- User accepts an invitation in Outlook and the invitation goes straight into the deleted items folder but does not go into the calendar. By default the invite should go into the deleted items folder since action was taken on it, but it should obviously go on the calendar as well.
That's my starting point. I'd shut down the BES and try to replicate the issue. If you can, then you have an Exchange/Outlook problem.
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright © 2004-2014 BlackBerryForums.com.
The names RIM © and BlackBerry © are registered Trademarks of BlackBerry Inc.