[kburd CH]

HI folks,
I have
BES 4.1 on 2000 server with system manager 2000
Exchange 2003 no sp yet on a 2003 server
users on Outlook 2003

On BES cdo.dll ver 6.5.6944 currently in system32 and registered in exchsrvr\bin

On Exch Server cdo.dll ver 6.5.6944 (this is not the latest version but I think you have to have the same cdo on both servers)

Mapi is same on both servers.
Permissions are pretty much dialed in... view only for administrative group object + send/receive as and administer info store for server object...

I get the dup calendar thing for a couple of users. Do they need to have anything done on their workstations? newer ver of cdo?
Should I install the latest SP for BES? help!

here are the logs

Event Type: Warning
Event Source: BlackBerry Messaging Agent BLACKB1 Agent 1
Event Category: None
Event ID: 20035
Date: 3/22/2006
Time: 8:36:27 AM
User: N/A
Computer: BLACKB
Description:
{user} CDOCalendar::UpdateAppointment - Exception handled.

Event Type: Warning
Event Source: BlackBerry Messaging Agent BLACKB1 Agent 1
Event Category: None
Event ID: 20216
Date: 3/22/2006
Time: 8:36:27 AM
User: N/A
Computer: BLACKB
Description:
{user@domain.COM} Synchronize() failed: ERR_FAIL, Tag=33891

Event Type: Warning
Event Source: BlackBerry Messaging Agent BLACKB1 Agent 1
Event Category: None
Event ID: 20035
Date: 3/22/2006
Time: 8:37:02 AM
User: N/A
Computer: BLACKB
Description:
{user} CDOCalendar::GetCDOAppointment - Exception handled.

Event Type: Warning
Event Source: BlackBerry Messaging Agent BLACKB1 Agent 1
Event Category: None
Event ID: 20035
Date: 3/22/2006
Time: 8:37:02 AM
User: N/A
Computer: BLACKB
Description:
{user} CDOCalendar::GetCDOAppointment - Exception handled.

Event Type: Warning
Event Source: BlackBerry Messaging Agent BLACKB1 Agent 1
Event Category: None
Event ID: 20216
Date: 3/22/2006
Time: 8:37:02 AM
User: N/A
Computer: BLACKB
Description:
{user@C-H.COM} Synchronize() failed: ERR_FAIL, Tag=33892

30000] (03/22 08:36:27):{0x5B4} Queuing alarm: BlackBerry Messaging Agent BLACKB1 Agent 1 (Application Event Log on BLACKB): 03/22/2006 08:36:27 (AFFF4E43) -> {user} CDOCalendar::UpdateAppointment - Exception handled.
[30000] (03/22 08:36:27):{0x5A0} Alarm::ThreadProc: Received an alarm message
[30000] (03/22 08:36:32):{0x5B4} EventLog::ThreadProc: Received notification, processing...
[30000] (03/22 08:36:32):{0x5B4} Queuing alarm: BlackBerry Messaging Agent BLACKB1 Agent 1 (Application Event Log on BLACKB): 03/22/2006 08:36:27 (AFFF4EF8) -> {user@domain.COM} Synchronize() failed: ERR_FAIL, Tag=33891
[30000] (03/22 08:36:32):{0x5A0} Alarm::ThreadProc: Received an alarm message
[30000] (03/22 08:37:02):{0x5B4} EventLog::ThreadProc: Received notification, processing...
[30000] (03/22 08:37:02):{0x5B4} Queuing alarm: BlackBerry Messaging Agent BLACKB1 Agent 1 (Application Event Log on BLACKB): 03/22/2006 08:37:02 (AFFF4E43) -> {user} CDOCalendar::GetCDOAppointment - Exception handled.
[30000] (03/22 08:37:02):{0x5A0} Alarm::ThreadProc: Received an alarm message
[30000] (03/22 08:37:02):{0x5B4} EventLog::ThreadProc: Received notification, processing...
[30000] (03/22 08:37:02):{0x5B4} Queuing alarm: BlackBerry Messaging Agent BLACKB1 Agent 1 (Application Event Log on BLACKB): 03/22/2006 08:37:02 (AFFF4E43) -> {user} CDOCalendar::GetCDOAppointment - Exception handled.
[30000] (03/22 08:37:02):{0x5B4} Queuing alarm: BlackBerry Messaging Agent BLACKB1 Agent 1 (Application Event Log on BLACKB): 03/22/2006 08:37:02 (AFFF4EF8) -> {user@domain.COM} Synchronize() failed: ERR_FAIL, Tag=33892
[30000] (03/22 08:37:02):{0x5A0} Alarm::ThreadProc: Received an alarm message
[30000] (03/22 08:37:02):{0x5A0} Alarm::ThreadProc: Received an alarm message
[30000] (03/22 08:39:41):{0x5B4} EventLog::ThreadProc: Received notification, processing...
[30000] (03/22 08:42:03):{0x5B4} EventLog::ThreadProc: Received notification, processing...
[30000] (03/22 08:42:03):{0x5B4} Queuing alarm: BlackBerry Messaging Agent BLACKB1 Agent 1 (Application Event Log on BLACKB): 03/22/2006 08:42:03 (AFFF4E43) -> {user} CDOCalendar::~CDOCalendar() - Exception handled.
[30000] (03/22 08:42:03):{0x5A0} Alarm::ThreadProc: Received an alarm message

[jibi]

from the BES 4.1 installation guide:

The version of the Microsoft Exchange System Manager tools that you install on the BlackBerry Enterprise Server must match the versionxxx8212;including service packxxx8212;that is on your messaging servers.

you need to match more than just the CDO.dll, so it looks like you may need to think about upgrading the OS and ESM.

[PacketRat]

on that discussion.. CDO versions.. Blackberry says it needs to match your exchange server but Microsoft says you should just have the newest one. MS says that the CDO.dll file doesnt talk to the other CDO.dll on your exchange machine its just a transport or client based tool that talks directly to exchange. you should always use the newest one.. Thoughts?

[stevebb]

We have always kept our BES's in sync with Exchange...
Matching cdo.dll and mapi32.dll. As well as any patches/hotfixes to the management tools.

So our file versions match.
Now, we also have both Exchange 5.5 and 2003... But we use the versions from the 2003 servers on our BES's... This hasn't caused issues for the few remaining 5.5 folks that I am aware of...

Steve

[kburd CH]

thanks Jibi, and guys as always...

So correct me if Im wrong.. BES 3.6 did not support ESM 2003 on a w2k server. I recently upgraded to 4 and as such the location of the registered cdo has changed from sys32 to the bin folder. I admit - its weird that some models get the dup and others dont. Its like 50-50 and not device specific. When we were on 5.5 it was rock solid throughout.

[Kablooey]

A version of the CDO.dll will be in the Exchange\Bin folder, but you need to register the file in the Windows\System32 folder. Otherwwise, you will receive an error when you install/upgrade the BES software.

[jibi]

Scratch what I said, somewhat (got slightly confused with the compatibilities). Just upgrade ESM as a whole on your BES (no need in upgrading the OS). And as Kablooey said, the location of CDO.dll needs to be in two different locations. With ESM 2000, it is not installed in Exchsrvr\bin, for whatever reason, thus you have to place it there from the Exchange server (in addition to \system32). With ESM 2003, it is installed with the package in Exchsrvr\bin.

- ESM should be installed to the default location: C:\Program Files\Exchsrvr
- CDO.dll should be registered at C:\Program Files\Exchsrvr\bin\cdo.dll
- A copy of CDO.dll should be placed (not registered) in WINNT\system32 or Windows\system32

In the event that you have installed BES on a 2003 server but are in an Exchange 2000 environment, you can install ESM 2003 on the 2003 server (ESM 2000 is not compatible on W2K3). CDO.dll is backwards compatible with previous versions, per Microsoft (hence the statement above about using the latest version).

[kburd CH]

whoops now Im confused:
Kablooey says a copy exists in bin but register in sys32 ...and you just said the opposite --> register in exchsvr\bin and put a copy in sys32.

My mail server is a separate win2k3 box with Exch2003
My BES is a win2k box w/ ESM 2000 in the default location

thanks guys

[jibi]

Per RIM installation documentation, register it in Exchsrvr\bin. Per RIM support, place a copy in \system32 to avoid errors/warning during installations/upgrades.

With BES 3.6, you had to register it in system32, if I'm not mistaken.

[kblinkhorn]

We are running BES 4.1 on windows server 2003 with ESM 2003. Our exchange box is server 2000 and exchange 2000.

what CDO version should we be running with exchange 2000 and on the BES box.

Where can I get the correct version?

Thanks.

[kburd CH]

in a nutshell: the esm version and cdo.dll ver should match on both boxes

uninstall ESM 2k3 on your BES server and install ESM 2000. Then your cdo.dll on each box should match. You can find the cdo.dll ver. on the exchange server by doing a search... By installing ESM 2000, you should be installing the identical cdo.dll. I seem to remember that in exch2000 you might have to copy the cdo to the correct spot. If somehow its not there or its different, just copy the cdo from the exch server over to the BES exch\bin and register it with the regsrvr32 command. Also place a copy in sys32.

not sure how this is affected by DST, but I think youre safe applying the windows 2k3 patch to your w2k3 box and performing the manual change on the w2k box.

[kburd CH]

and to follow up on the vers of cdo.... what sp do you have on exch 2000? remember to patch the esm on the bes to the same sp and apply any and all hotfixes that you have applied to the exchange server

[newbnet]

I have the same CDO.DLL version on Exchange and Blackberry server.

exchsrv\bin\cdo.dll *register at blackberry and Exchange server

windows\system32\cdo.dll *not register at Blackberry and Exchange server



I have the same mapi.dll version at Exchange and blackberry server too.

do I need to register mapi32.dll?


because I am not sync from Blackberry devices to Exchange but if I add something to calendar from exchange to devices it works fine.

Blackberry version 4.0.6
Exchange 2003 with windows server 2003

I need help

[kburd CH]

Before you do anything else you should apply the SPs to at least get to 4.1 on both BES and the handhelds. Then make sure you have the same SP applied to Exchange, ESM and ESM on the BB.