BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 03-01-2006, 03:16 PM   #1 (permalink)
New Member
 
Join Date: Mar 2006
Location: Virginia
Model: 7250
Posts: 12
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default CDO and MAPI32 help for Wireless Calendar Sync

Please Login to Remove!

Not a BES Admin, trying to find the answer to this problem because the BES admin folks either can't seem to or don't want to.

Looked through the posts, found lots of info, just didn't find any specific to our situation. Need some questions answered, please.

Problem:
Wireless calendar sync doesn't work right, mostly works in one direction

Environment is:
BESv4.0.3 on a Win2003 server
Exchange 5.5 servers on Win2000 servers (Exchange 2003 coming, sure that will mess stuff up then)

Because the OS on the BES is Win2003, they installed Exchange2003, so:
CDO.dll version on the BES is 6.5.6980.3, MAPI32.dll is 6.5.6944.0
CDO.dll version on Exchange 5.5 server is 5.5.2653.12, MAPI32.dll is 5.5.2653.12


Questions:
How do they get the CDO.dll/MAPI32.dll files to the same version?
Can the CDO.dll and MAPI32.dll files from Exchange be registered on the BES, given that Exchange 2003 is installed, and if so where, as the C:\exchsvr\bin folder does not exist on the BES? Just create the folder and register there?
Or can you update the CDO.dll/MAPI32.dll files on the multiple Exchange 5.5 servers to the version that currently resides on the BES?

Any help would be appreciated. When I brought up the problem to the BES admin folks, they told me to call the service provider, so I started looking into it. Have an important user that needs this fixed, can't wait for them to get off their butts and call RIM.
Offline  
Old 03-01-2006, 05:35 PM   #2 (permalink)
BlackBerry God
 
jibi's Avatar
 
Join Date: Oct 2004
Location: Jibi's Secret Place
Model: 8900
OS: 4.6.1.174
Carrier: AT&T
Posts: 11,310
Post Thanks: 0
Thanked 1 Time in 1 Post
Default

CDO.DLL is backwards compatible, so as long as the version on the BES is higher than the version being used on the Exchange server, there *should* be no issues (some others will disagree - simply going by what RIM has told me).

Updating the Exchange patch level (or service pack level) on the BES for ESM should update MAPI32.DLL and CDO.DLL to the same version number (or within a point or so off). You will not want to register anything from an Exchange 5.5 server onto a Windows 2003 server running BES.

If this is affecting more than just yourself, your BES administrators should put in a support ticket with RIM, or at the very least, attempt to troubleshoot the issue. Then again, they may just be waiting until the Exchange 2003 migration (from 5.5, its a pretty major upgrade).
__________________
In the beginning the Universe was created. This has made a lot of people very angry and is widely regarded as a bad move.
Offline  
Old 03-01-2006, 05:48 PM   #3 (permalink)
Talking BlackBerry Encyclopedia
 
Join Date: Apr 2005
Location: The Netherlands
Model: 8800
Carrier: Vodafone
Posts: 374
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Your configuration is not supported. With Exchange 5.5 you must install your BES on NT4 or better, Windows 2000. Then you need to install the Microsoft Exchange 5.5 System Administrator on that machine (where you get the C:\exchsvr\bin). The CDO on the BES and Exchange must be 5.5.2657.55 and MAPI32 5.5.2653.12.

For more info: Wich CDO.dll version you need for the BlackBerry Enterprise Server (BES)?

See also the Quick Start Guide in the Docs directory under your BES installation directory.

Regards,
Bob
Offline  
Old 03-01-2006, 08:04 PM   #4 (permalink)
BlackBerry God
 
jibi's Avatar
 
Join Date: Oct 2004
Location: Jibi's Secret Place
Model: 8900
OS: 4.6.1.174
Carrier: AT&T
Posts: 11,310
Post Thanks: 0
Thanked 1 Time in 1 Post
Default

Of course, as mentioned in my last post, depending on who you ask on here (and I'm sure at RIM), as long as the version of CDO is higher on the BES than it is on Exchange, you will not have issues. 2003 ESM on the BES is supported (by RIM) running on Windows 2003 in an Exchange 2000 environment running on a Windows 2000 server.

Just have someone contact RIM.
__________________
In the beginning the Universe was created. This has made a lot of people very angry and is widely regarded as a bad move.
Offline  
Old 03-02-2006, 08:23 AM   #5 (permalink)
New Member
 
Join Date: Mar 2006
Location: Virginia
Model: 7250
Posts: 12
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks for the info, both of you.
I suspect it is a problem with the Exchange 5.5 server that the affected people are on.
I am on a different Exchange 5.5 server and it works fine for me.
I guess when they get with RIM they can maybe find out what it is.
Offline  
Old 03-02-2006, 01:44 PM   #6 (permalink)
New Member
 
Join Date: Mar 2006
Location: Virginia
Model: 7250
Posts: 12
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

From the log, the error the users are having looks like this, those we have found having trouble are on the same Exchange server.

[30001] (03/01 00:18:32):{0xC0C} CDOCalendar::Initialize - Code = 80040705, WCode = 0505, Code meaning = IDispatch error #1285,
[30002] (03/01 00:18:32):{0xC0C} Server = EXCHANGE, Mailbox = /o=ORGANIZATION/ou=XXXX/cn=Recipients/cn=XXXX/cn=username Description = The attempt to log on to the Microsoft Exchange Server computer has failed. [Microsoft Exchange Server Information Store - [MAPI_E_FAILONEPROVIDER(8004011D)]].
[30180] (03/01 00:18:32):{0xC0C} {username} CDOCalendar::Initialize - Error in call m_spCalendarFolder = m_spCDOSession->GetDefaultFolder.
Offline  
Old 03-02-2006, 07:23 PM   #7 (permalink)
BlackBerry God
 
jibi's Avatar
 
Join Date: Oct 2004
Location: Jibi's Secret Place
Model: 8900
OS: 4.6.1.174
Carrier: AT&T
Posts: 11,310
Post Thanks: 0
Thanked 1 Time in 1 Post
Default

http://www.blackberry.com/knowledgec...25232&vernum=0

Hope that helps. Looks like its a permissions issue. Tell your BES Administrators they should be fired, honestly. Its horrible when someone else that doesn't have access to the server has to take the initiative to get a resolution for the issue... absolutely pathetic!
__________________
In the beginning the Universe was created. This has made a lot of people very angry and is widely regarded as a bad move.
Offline  
Old 03-02-2006, 07:38 PM   #8 (permalink)
dev
CrackBerry Addict
 
dev's Avatar
 
Join Date: Apr 2005
Location: Toronto
Model: 8800
Carrier: Rogers
Posts: 571
Post Thanks: 0
Thanked 2 Times in 2 Posts
Default

Your log errors indicate a permissions problem with the BES service account on the Exchange server information store. Have the admins do a comparison of the users that work against does that don't. Shouldn't take long to do.
Offline  
Old 03-02-2006, 07:41 PM   #9 (permalink)
BlackBerry God
 
jibi's Avatar
 
Join Date: Oct 2004
Location: Jibi's Secret Place
Model: 8900
OS: 4.6.1.174
Carrier: AT&T
Posts: 11,310
Post Thanks: 0
Thanked 1 Time in 1 Post
Default

...and then recommend they go find new jobs...
__________________
In the beginning the Universe was created. This has made a lot of people very angry and is widely regarded as a bad move.
Offline  
Old 03-03-2006, 08:25 AM   #10 (permalink)
New Member
 
Join Date: Mar 2006
Location: Virginia
Model: 7250
Posts: 12
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks all.
I sent the BES Admin that RIM KB about the permissions yesterday and they finally called RIM, but I was told that they checked into it with RIM and that was not the issue.
It's weird because the text in the error is "The attempt to log on to the Microsoft Exchange Server computer has failed." instead of "You do not have permission to log on." Not sure what would cause the access problem with the information store if the permissions were correct.
They are planning on decommissioning that server soon, so the solution is going to be to move any BES 4.0 users off of that server.
Offline  
Old 03-03-2006, 08:57 AM   #11 (permalink)
Talking BlackBerry Encyclopedia
 
Join Date: Apr 2005
Location: The Netherlands
Model: 8800
Carrier: Vodafone
Posts: 374
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

not trusted domains / machines is maybe the problem...

Regards,
Bob
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.