[coconinocounty]

I have following dlls -

BES

mapi32.dll - 6.0.6249.0
cdo.dll - 6.0.6617.47

Exchange 2000

mapi32.dll - 6.0.6617.47
cdo.dll - 6.0.6617.47

I have tried to apply update rollups for Exchange for KB840540 and KB836488. Both error with message that they can be applied to Exchange 2000 Build 4417 only. How do I update my mapi32.dll so it matches all the others?

[hdawg]

Welcome to the forums ...

If your OS on your BES is indicating that it cannot install the patch because it isn't appropriate for the version of software installed, then it can't be installed.

You could use regsvr32 to unregister the mapi32.dll, copy it over from the Exchange server, overwrite the dll, and then re-register it on your BES.

More importantly though ... were you able to apply this patch to Exchange and not BES?

Even more importantly ... time to upgrade; Exchange 2000 is past its time.

[Ugg]

The version numbers that you're seeing on an Exchange 2000 BES match what I saw the last time I did a BES / Exchange 2000 upgrade. I think that it's a foible of the updates available from Microsoft for various Exchange components that leaves you with a lower MAPI32.DLL version on the BES.

Is something not working that suggests that you need to do a further update?

[coconinocounty]

Thanks for the info hdawg. We are in the process of planning an upgrade to Exchange 2007. No issues with doing a manual copy and registration of mapi32.dll?

Ugg, I just attended BES training and the trainer stressed the importance of all dll's matching between BES and Exchange server.

Thanks both.

[hdawg]

Originally Posted by coconinocounty

Thanks for the info hdawg. We are in the process of planning an upgrade to Exchange 2007. No issues with doing a manual copy and registration of mapi32.dll?

Ugg, I just attended BES training and the trainer stressed the importance of all dll's matching between BES and Exchange server.

Thanks both.

Everyone says it works ... I've never once manually registered dll's.

[gibson_hg]

I would not move MAPI32.dll manually.

I had a call from people managing 2 BES for Homeland Security and it fubared both of them. They proceeded to blame a RIM KB but failed to provide us the KB number, dumbasses! You will end up removing ESM and re-installing it to get MAPI working. Save yourself the headache and find the correct updates, start with installing SP3 if you haven't and the apply the SP3 rollups.

Keep in mind that MAPI is a subsystem and consists of more than MAPI32.dll, other files also update.

As far as I know Exchange 2000 goes as high as SP3 then there are rollups rather than SP's.

Let us know what you find.

[coconinocounty]

Thanks gibson. Now I have a really dumb question. I have my Exchange 2000 tools installed on a Windows 2003 server. The Exchange install and the SP3 install barked at me but let me go through. Tried to install a rollup and had no luck. Think this is a function of running Exchange 2K on unsupported OS?

[hdawg]

you're better off removing the Exchange 2000 tools and installing the 2003 SP2 tools ...