[Lakeros]

Very new to the BES server. Looking for any information that will help me get my clendars syncing correctly. create a calendar event in outlook and sync's fine to handheld, create an event on the handheld will not show in outlook.
handheld - 7520
worked correctly in exchange 2000 but recently moved account(s) to exchange 2003 sp1 cluster
exchange server and server with BES have same CDO.dll mapi.dll has been changed to the new server

any help would be greatly appreciated

[BlackBerryLinks]

I have seen more problems with the CDO 6.5.7226.0 from MS Exchange with SP1. You can obtain from Microsoft (by request?!) a hotfix with CDO
21-Jun-2005 02:37 6.5.7233.28 709,120 Cdo.dll

If you search on Microsoft on 6.5.7233.28 you find more possible problems with the CDO.

"When you try to retrieve appointments in a CDO-based program that is running on an Exchange Server 2003 server, the CDO-based program may stop responding"
http://support.microsoft.com/?scid=kb;en-us;867446

You can also try to downgrade the CDO on the BES to CDO version 6.5.6980.3
http://blackberry-links.com/ms-cdo.dll-6.5.6980.3.html


Regards,
Bob

[Lakeros]

Thank you for the info. I will give it a try and see how it goes.

[Lakeros]

I updated the CDO.dll from microsoft and that did not seem to correct the issue. Again if anyone can help me figure out why it will sync from the desktop to the handheld but not from th handheld it would really help. Thanks in advance.

[jibi]

which version of ESM do you have on the BES server?

[jdh]

Another possibility is that the BES Admin user (the user that the BES Services are running as) has insufficient rights to the Exchange mailboxes... The BES Service account needs specific permissions to the Exchange mailboxes that it's going to manage in order to create calendar entries in them.

See the following article on RIM's support site for more info:

http://www.blackberry.com/knowledgec...990&vernum=5#5

(scroll down to the section that describes "Insufficient Permissions")

[jibi]

i think if that was the case, the issue would have been present with Exchange 2000, as well.

[Lakeros]

If ESM=Enterprise server manager i am on version 4.0.0.116. I apologize for being such a newbie i just was handed this yesterday. Thanks again for any help

Thanks Jibi and JDH for the replying

[jibi]

Exchange System Manager

My hunch is the BES still has ESM2K installed on it. If it does, uninstall it. Install ESM2K3 (from the Exchange 2003 CD) to the default location (C:\Program Files\Exchsrvr). Register the CDO.dll (regsvr32 "c:\program files\exchsrvr\bin\cdo.dll"). Once completed, apply the Exchange 2003 SP1 patch to the installation. Once thats done, copy the CDO.dll to C:\Windows\System32 directory.

Once thats done, I'd recommend upgrading the BES to 4.0 SP2, but thats just an optional step.

[jdh]

Originally Posted by jibi

i think if that was the case, the issue would have been present with Exchange 2000, as well.

Not necessarily, as the rights to the message stores on the Exchange 2003 server could be different from the Exchange 2000 server.

If the rights have been properly granted at the top level, this shouldn't be an issue, but I've had a couple of clients who have upgraded to Exchange 2003 only to find that their Administrative rights haven't been applied properly to their new Exchange 2003 storage groups.

This can be especially true if the BES or Exchange Admin accounts are members of groups that may have an explicit "Deny" privilege within the new storage groups.

[Lakeros]

Jibi and JDH -
After spending almost 3 hours on the phone with tech support it turned out to be a rights issue. BESAdmin account had to much rights - i know sounds crazy but it solved the issue. The BESAdmin had full contol rights, did not have domain admin rights which causes a deny for receive as and send as rights. When we reduced the rights to just - Read, Execute, Read Permissions, List Content, Read Properties, List Objects, Admin Info Store, View Info Store Status, Receive As, Send As everything started to work fine - calendars now sync both ways. Thank you again for all your suggestions, i hope soon to contribute here as i gain more insight to the BES server.

[SteelBES]

Originally Posted by Lakeros

Jibi and JDH -
After spending almost 3 hours on the phone with tech support it turned out to be a rights issue. BESAdmin account had to much rights - i know sounds crazy but it solved the issue. The BESAdmin had full contol rights, did not have domain admin rights which causes a deny for receive as and send as rights. When we reduced the rights to just - Read, Execute, Read Permissions, List Content, Read Properties, List Objects, Admin Info Store, View Info Store Status, Receive As, Send As everything started to work fine - calendars now sync both ways. Thank you again for all your suggestions, i hope soon to contribute here as i gain more insight to the BES server.

OK, BES newbie here too (and Exchange newbie as well.) I'm having the same problem as you and I've read over and over about the rights for the BESAdmin account, but how do you know which account is the BESAdmin? I really don't want to call TS.... ;) I'm sure this will fix my problem as well.

Thanks.

Update: FYI - I figured it out on my own. I checked a few more forum posts here and found out that I didn't add a BESAdmin account when I installed the BES, so the Blackberry services are running as Administrator. Microsoft SBS 2003, by default, does not allow the Administrator to have "Send As" and "Receive As" privildges in Exchange. You cannot change or delete these entries either, but I got around it by just adding second entries for "Send As" and "Receive As" and set them to Allow. I realize this isn't the best case for security, but it did fix the Calendar Sync problem. Now that I know the sync'ing worked, I can reinstall the BES Enterprise software correctly with the BESAdmin account. Thanks!

[greywolfe]

*cough*preinstall tasks*cough*

[jibi]

Originally Posted by greywolfe

*cough*preinstall tasks*cough*

what are those?

[greywolfe]

Originally Posted by jibi

what are those?

Thats the usual response, yes :(

[ctrl+alt+del]

Originally Posted by jdh

Another possibility is that the BES Admin user (the user that the BES Services are running as) has insufficient rights to the Exchange mailboxes... The BES Service account needs specific permissions to the Exchange mailboxes that it's going to manage in order to create calendar entries in them.

See the following article on RIM's support site for more info:

http://www.blackberry.com/knowledgec...990&vernum=5#5

(scroll down to the section that describes "Insufficient Permissions")

The posting above resolved a problem with a new BES server install where calendar new appointments/edits via blackberry were not synchronizing back to Exchange/Outlook, but Outlook new appointments/edits were ok back to the blackberry.

I just wanted to express thanks to JDH. I was about to replace the cdo.dll file, but fortunately saw this first, and decided to check the privileges of the BESAdmin account on the Exchange server. There were only two checkmarks missing under one area, but that was all that was needed to cause/resolve the problem.

Thanks again.

[Miche_kna]

Hi There!

This is my first post in this forum so I hope that I can describe my problems correctly!

Anyway... I manage our BES-Server in out organization and are experiencing the same problems with the calendar function.

I´ve checked CDO-versions - they match and have been registred.
I´ve checked the BES-admin account rights and run the IemsTest.exe and everything works as it should.

The only last thing I can relate this problem to is that we have multiple Addresslist in our Exchange enviroment.

We have the followin addresslists:
--------------------------------------------------------

Admin -> Includes all the administrative employees.
School -> Includes all educational personel and students
Company -> The companies that belongs to us.
--------------------------------------------------------

The users on the BES-Server that belongs to the Admin-addresslist have a fully operational calendar.

The users that belongs to the Company-addresslist cant sync their calendar properly.

When I add a new user in BES-Manager the Global Addresslist cant find the users in the Company-addresslist.

Is there any workaround for this problem?

BTW... The personel from the companies have their mailboxes on the same servers as the regular admin-personel...

Hope I made my self understood!

[Miche_kna]

Problem solved!

Changed the permissions on the addresslists that the BES-admin account colud list.

[exiled]

Changed them to what? And where

Originally Posted by Miche_kna

Problem solved!

Changed the permissions on the addresslists that the BES-admin account colud list.

[Miche_kna]

Originally Posted by exiled

Changed them to what? And where

Removed the BES-admin account from the default Addresslist-policy that we have in our AD.
Added rights to the correct addresslist in Exchange System manager for the BES-admin account.