BlackBerry® Enterprise Solution

[snorket]

I actually have 2 MAGT log files. I guess one is for each agent since there are 2 exchange servers. I checked the log and this is what I found:

MAGT_01 (mailbox agent 1. this one looks its for the singapore exchange server as it only contains entries for singapore users)

[30000] (10/19 00:00:09.230):{0xD14} [ENV] MAPI32.DLL: C:\WINDOWS\system32\MAPI32.dll, Version: 6.5.7654.12
[30000] (10/19 00:00:09.230):{0xD14} [ENV] CDO.DLL: C:\Program Files\Exchsrvr\bin\cdo.dll, Version: 6.5.7654.12

MAGT_02 (mailbox agent 2. malaysia exchange server as it only contains entries for the malaysia user)

[30000] (10/19 00:00:09.460):{0xCD8} [ENV] MAPI32.DLL: C:\WINDOWS\system32\MAPI32.dll, Version: 6.5.7654.12
[30000] (10/19 00:00:09.460):{0xCD8} [ENV] CDO.DLL: C:\Program Files\Exchsrvr\bin\cdo.dll, Version: 6.5.7654.12

[30180] (10/19 00:00:23.894):{0xBCC} {elsielow} CDOCalendar::Initialize - Error in call m_spCalendarFolder = m_spCDOSession->GetDefaultFolder
[40000] (10/19 00:00:23.894):{0xBCC} CDO initializing failure in CDO helper 00cf7610 (5)
[40580] (10/19 00:00:24.953):{0xBCC} CDO helper 00cf7610 closing after CDO initialize failure
[40000] (10/19 00:00:25.053):{0xBCC} CalHelper failed 00cf7610, ErrorCode = -11, Thread activity was Checking CDO object list
[40577] (10/19 00:00:26.601):{0xBCC} CDO helper 00cf7610 stopped

The cdo.dll in the malaysia exchange server is D:\Exchsvr\bin, so the agent is pointing to the wrong path. How do I change this?

[OzBBerry42]

Hi,

So all CDO.dll's are pointing to  C:\Program Files\Exchsrvr\bin\cdo.dll which is the correct location.

The Exchaneg server can have whatever location it wants, as long as the BES's have an equal or  later version of mapi and cdo.dll's.

What version of mapi and cdo does the malaysian Exchange server have?

[snorket]

cdo.dll and mapi32.dll are both 6.5.7654.12 on the malaysia server. This is the same version as the files on the BES and the singapore exchange server.

But the registry key that confirms that the cdo.dll is registered is missing on the malaysia exchange server. The key is present on both the BES and the singapore exchange server. Could this be the problem?

[OzBBerry42]

The only way I know of is to do a reinstall...

Run the uninstall program and see if you can do a "Repair" on it....

[snorket]

Err...You're talking about reinstalling the BES and not Exchange, right?

[OzBBerry42]

Yes.

[xcrunner]

I found the post yesterday as I was having issues with accepting calendar invites on the blackberry after migrating from SBS 03 to SBS 08.

After seeing that you were missing the CDO registry key in one of your exchange servers.  I checked mine and it was missing as well.

Instead of having to do a reinstall of BES, I ran the mapi cdo file install on the SBS 08 server, 

http://www.microsoft.com/downloads/details.aspx?FamilyID=E17E7F31-079A-43A9-BFF2-0A110307611E&displa...

Restarted blackberry server services and had the users reboot thier blackberry devices, the issue was resolved.

I would try a repair of Exchange 2003 on the server missing the cdo.dll registry.

[OzBBerry42]

Hi,

Thanks for that.

That file (exchangemapicdo.exe) will upgrade the CDO and mapi files. Since all the files match there is really no need to update the files to newer versions, but if it fixed the registry entry then Id say, yes, give it a try.

It certainly WONT hurt to install it, thats for sure.

And it may even help!

[snorket]

I really would have loved to try this fix, unfortuantely the KB article states:

"This package will not install on a system on which any version of Microsoft Outlook or Microsoft Exchange Server 2003 or earlier is installed."

My exchange version is 2003 SP2

Abyway, I've registered the cdo.dll on the malaysia exchange and confirmed the creation of the required registry key, then restarted the BES. Now I'm waiting for the user to reset her blackberry. Hope this works.

[snorket]

Well, it looks like re-registering the cdo.dll on the malaysia exchange didn't work. Looks like the only thing left to do is reinstall the bes, and even then I'm not so sure that it will work.

ANyway, thanks for all the help!