View Full Version : Unable to sync Calendar two-ways - hlep!!

03-14-2005, 08:47 PM
:bb: I am running on a BES 4.0 and a BB 7290 also on version 4.0. I can sync my email, Tasks, and Memo's between Outlook (Exchange) and my BB just fine. However, I am having a problem with Calendar items.

With Calendar items I can create them in Outlook and they will show up on the BB. If I create them on the BB, they never show up in Outlook.

If I delete an item in Outlook, it is deleted on the BB. But if I delete an item created in Outlook that is on the BB, it will not delete in Outlook.

Under calendar options (on the BB) I have Wireless Sync set to ON and in Intellisync, PIM, Calendar, I have it set that BB Wireless Sync Wins.

What am I doing wrong, what setting(s) need to change?

Many thanks in advance.



03-14-2005, 10:38 PM
this is a permission issue. the service account does not have full rights to the information store. ask your administrator to fix this.

03-14-2005, 11:13 PM
unfortunately, I am the adminstrator.....sort of. I use MailStreet for both Exchange and BES.

What can as the user do????


03-15-2005, 09:49 AM
I would contact mailstreet. They should be able to help you.

03-18-2005, 08:04 PM
this is a permission issue. the service account does not have full rights to the information store

I'm having the same problem. Any guidance on how to set the rights?

Thank you in advance!!

03-18-2005, 11:40 PM
I had this exact same problem with Mailstreet this week, from about Saturday (Mar 12) to Wednesday (Mar 16). I had contacted Mailstreet support, and they initially walked me through some of the more obvious options (which I had already tried), including wiping out my Service Book and redoing my Enterprise Activation.

On Wednesday, they finally admitted that they had been having some problems with the server, and that it had been fixed. Since then, my wireless calendar sync has been working fine.

If you're still having this problem, I'd recommend calling/e-mailing Mailstreet support, as it's possible some accounts or servers might still be having the same issue.