[DarienA]

Hey folks, let me give you a quick rundown of our scenario. Our servers run Exchange 2003 SP1 and BES 4.0.

I've been here(new job) for about a month now and recently have seen a higher number of cdo related errors on the event viewer. In doing some snopping around I've discovered a few issues that I need your help on resolving.

First off the organization previous ran Exchange 5.5 and it looks like the cdo.dll that is in the system32 folder on the BES is the 5.5 .dll it's version 5.5.2655.79. Our ESM tools are installed on the D drive of our BES and the cdo.dll there is version 6.5.6944.0. The same goes for the mapi32.dll.

I'm guessing that the 5.5 means that the ESM tools are still the 5.5 tools because when I downloaded the Exchange 2003 SP1 to run on the BES the service pack said it could not FIND Exchange 2003.

So my questions are:

1. Am I guessing correctly that yes the reason the dll's in the system32 folder are version 5.5.2655.79. Is because when ESM first installed on the BES it was down with version 5.5 and never upgraded?

2. If that's the case does the following accurately describe what I need to do to bring all my dll's current?

A. Install Exchange 2003 ESM on the BES.
B. Install Exchange SP1 ESM on the BES.
C. Verify that the installed map32 and cdo dll's on the BES are now the same version as the ones on our Exchange Server.
D. Manually register the cdo.dll that is in the bin folder, place a copy of the cdo.dll in the system32 folder.

3. Do I need to manually register the mapi32.dll?
4. Once I've done that should I then look at installing any hotfixes and service packs we are missing and if so should I go all the way up the newest hotfix?


Thanks for your help/suggestions, etc.

[BlackBerryLinks]

Originally Posted by DarienA

So my questions are:

1. Am I guessing correctly that yes the reason the dll's in the system32 folder are version 5.5.2655.79. Is because when ESM first installed on the BES it was down with version 5.5 and never upgraded?

2. If that's the case does the following accurately describe what I need to do to bring all my dll's current?

A. Install Exchange 2003 ESM on the BES.
B. Install Exchange SP1 ESM on the BES.
C. Verify that the installed map32 and cdo dll's on the BES are now the same version as the ones on our Exchange Server.
D. Manually register the cdo.dll that is in the bin folder, place a copy of the cdo.dll in the system32 folder.

3. Do I need to manually register the mapi32.dll?
4. Once I've done that should I then look at installing any hotfixes and service packs we are missing and if so should I go all the way up the newest hotfix?


Thanks for your help/suggestions, etc.

1) Correct
2) Yep, see also:
http://blackberry-nl.com/index.php/topic,206.0.html

3) No
4) Better first wait some days, and see what is the result of updating the CDO...

Step by Step

Regards,
Bob

[DarienA]

Thanks BBL my event log is much clearer this morning.... only one new error and its and SRP localhost related error which I hadn't seen before. From a quick scan of various message threads it looks like its a problem that a later hotfix will resolve so I'll wait til the end of the week and then bring myself current. I'm assuming by applying the latest SP is cumulative of previous SP's and hotfixes? Is that the same with hotfixes or will I need to apply all hotfixes after the most recent service pack?