[dhahlen]

I've done the steps here:

BlackBerry Search Results

I've updated the MAPI on both EX07 and BES Server.
-BES is Win Svr 2003 Standard SP2
-Ex07 is Win Svr 2003 standard x64 SP2

I've reset the MAPI profile for BES as well, I've tried multiple users, and ensured wireless calendar sync is enabled on the blackberry as well as the server.

E-Mail works fine, bidirectional, and wireless

The besadmin account has the correct permissions which were given through the exchange management shell - I've verified them again this morning.

I've updated BES to the latest version and I can't figure out why the calendar sync will not work at all. I've tried placing an appointment on outlook to see if the BB would sync, no luck. I tried placing it on the BB to see if Outlook would see it, nothing.

Any assistance in getting the calendar sync to work would be greatly appreciated.

Going to EV - just noticed these two when restarted services:

MailboxManager::GetFreeBusyFolder - OpenEntry (0x8004010f)
MailboxManager::SubsystemInitialize - GetFreeBusyFolder (0x8004010f)

These two errors seem to deal with meeting regeneration on the BB - which is a small issue. However, I am not sure if it relates to the calendar sync function not working overall.


Thanks,
Darren

[dhahlen]

Checked besadmin account permissions on EX server

It has the following groups assigned:

-Domain Admins
-Domain Users
-Exchange View-Only Administrators

I added this group as it fixed a one-way sync problem for another user, my issue is calendar sync both ways but I figured this was worth a shot

-Exchange Public Folder Administrators

[penguin3107]

The BES admin account should not be a domain admin.
(Not sure if that's the root of your problem, but you should fix it anyway.)

[dhahlen]

I've read that a few places as well - as I did not initially set up the server I left it there. I've just removed the domain admin account - we'll see how that goes.

[dhahlen]

Removed domain admin, added Exchange public folder admin - seems to be working for all users, bidirectional!

Thanks

[dhahlen]

Seems it not working for another user now... troubleshooting that. Oh, the reason it had domain admin is because it's on a domain controller. You can't login to the ADC unless you're a member of the domain admins group. Thats how the current GP is setup, I suppose would could modify it for use with besadmin account - but are there any reasons why BES shouldn't have domain admin?

[penguin3107]

That's the reason why you're not supposed to install BES on a Domain Controller.