Encams
asked on
Wireless calendar sync problems
BES3.6 installed on Windows 2000
Exchange 5.5 installed on NT4
Clients using Blackberry v4 handhelds and Outlook 2003 on XP Pro SP2
If an entry is made in Outlook calendar it will sync to the BlackBerry device wirelessly but when an entry is made on the BB itself it doesn't not wirelessly sync that to Outlook.
The user does have wireless sync enabled.
Urgent, 500 points.
Exchange 5.5 installed on NT4
Clients using Blackberry v4 handhelds and Outlook 2003 on XP Pro SP2
If an entry is made in Outlook calendar it will sync to the BlackBerry device wirelessly but when an entry is made on the BB itself it doesn't not wirelessly sync that to Outlook.
The user does have wireless sync enabled.
Urgent, 500 points.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Checking the BES server logs i see the following error:
[30001] (05/16 13:31:46):{0x730} *** CDO *** CDOCalendar::Initialize - Code = 800406f9, WCode = 04f9, Code meaning = IDispatch error #1273,
[30002] (05/16 13:31:46):{0x730} Server = ntbdc01, Mailbox = /o=tbg/ou=site1/cn=Recipie
[30180] (05/16 13:31:46):{0x730} {BESadmin} CDOCalendar::Initialize - Error in call m_spCalendarFolder = m_spCDOSession->GetDefault
[40000] (05/16 13:31:46):{0x730} CDO initializing failure in CDO helper 02e912d8 (1)
Which is why the appointments never seem to make it back to Outlook.
Running the IEMStest.exe in the utility folder on a mailbox, it connects to the mailbox, makes it's folder and can delete it succesfully everytime:
BlackBerry Enterprise Server Utility - IEMSTest.exe (IExchangeManageStore), Version 1.0
Copyright (c) Research In Motion, Ltd. 1999. All rights reserved.
Opening Default Message Store Mailbox - BESAdmin.
Opening message store for BESAdmin using /o=tbg/ou=site1/cn=Recipie
in /o=tbg/ou=site1/cn=Configu
DB.
BESAdmin's Mailbox opened successfully.
Root Folder opened successfully.
Folder created successfully.
Test folder deleted successfully.
Test completed successfully for BESAdmin.
I think the problem could have something to do with when trying to use the Exchange 5.5 admin tools, i get the following error when trying to connect to my Exchange server:
A connection could not be made to the microsoft exchange server computer XX_XX_XX
The Microsoft exchange server computer does not respond.
Microsoft Exchange Directory
ID no: DS_E_COMMUNICATIONS_PROBLE
Which is a recognised problem from Microsoft in 56bit and 128bit encyption being passed between NT and 2000 server. Sadly MS don't support NT4 anymore so you can't get hold of the patch.
So has anyone been able to get it working in a similar enviroment?
Sorry for the length of the post, i'm hoping someone will recognise all the symptoms and be able to tell me how they beat it, plus you'll be doing better than O2 and RIM who are both stumped by the problem at the moment :)
Thanks,