Link to home
Start Free TrialLog in
Avatar of proactiveit
proactiveitFlag for United States of America

asked on

How do I enable Bidirectional Wireless Calendar Synchronisation

After installing and configuring BES 4.1, everything is working great apart from the fact that the Wireless Calendar Sync seems to be only from Server to device and not bidirectional. Is there an option to enable Bidirectional sync for the Calendar.

Thanks in advance for any suggestions
ASKER CERTIFIED SOLUTION
Avatar of mickeyfan
mickeyfan

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of proactiveit

ASKER

I am running SBS 2003 and I have assessed the versions of cdo.dll, ther is only 1 file which is located in the Exchsrv\Bin and another copy whcih is pushed out through ClientConnect to all client PCs when joining the domain.

Exchsrvr\Bin\cdo.dll - v6.5.7638.2
ClientApps\outlook2003\FILES\PFILES\COMMON\SYSTEM\MSMAPI\1033\cdo.dll - v6.5.6980.74

There is No cdo.dll in the System32 directory, should I copy the cdo.dll from the Exchsrvr directory and then register it?

I also would have thought that the version on the exchange server would have had to be the same as the workstations\Outlook clients
This can be caused by a corrupt service book.  You can delete and resend the service book from the BES.

right click on the user and click on send service books

Make always sure that your BES is always at the same patching level as your exchange servers.
Do NOT copy any files from the exchsrvr/bin into your system32. I strongly recommend upgrading your windows OS & exchange server/BES to exchange 2003 SP2 and running the DST update then doing a start > run > cmd: regsvr32 "c:\program files\exchsrvr\bin\cdo.dll". Your cdo.dll version should be 6.5.7651.61 if properly patched with the DST update (http://support.microsoft.com/kb/926666). I have seen this cause issues with bi-directional sync on 2 BES servers (out of 200) and even if it's not the root cause of the issue it's simply just good to do.

Are all users experiencing this issue or only one user? BES 4.1.x by default enables wireless bi-directional calendar sync globally. If one user is having the issue I would start by removing them from BES and deleting their user data when prompted. If ALL users are experiencing the issue that's another story. What errors do you see in the BES server application eventvwr? Sometimes everything on BES is configured fine but the calendar service book is bad. From the handheld go to options > advanced > service books & delete the Desktop [CICAL] service book. Wait about 30 sec then go into your BES server then resend the IT policy & service books to that user.

If none of the above resolves the issue please let us know.


~ CFJ
I performed the following which resolved the issue,

1. Registered cdo.dll %WINDIR%\System32
2. Configured Permissions for BESAdmin to Exchsrvr Directory
3. Configured Permissions for BESAdmin - ESM\Server
4. Resent Service Books
5. Resent Policy

I am pretty sure it was the permissions, anyway all tested fine. I am interested in your views whether to leave cdo.dll in the System32 directory. Also the BES is installed on a SBS 2003 machine which is fully patched apart from the DST patch which I will install first chance I get.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
BTW - registering the cdo.dll in system32 did nothing for you - your issue was permissions related.


~ CFJ
I do agree with it being permissions and I will also remove the cdo.dll from the system32 directory. I am going to split the points with Mickeyfan for the solution and Monorail1 because he provided some valuable info.

Thanks