• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 890
  • Last Modified:

Exchange detected that "C:\WINNT\system32\MAPI32.dll" is not the correct version required

I have Exchange 2000 installed on W2K server w/ GFI Mail Security and GFI Mail Essentials. Everytime I open ESM I get this error that pops up:

Exchange detected that "C:\WINNT\system32\MAPI32.dll" is not the correct version required to run Exchange System Manger or Exchange 2000 Server. This may cause failures in Exchange System Manager, affect availability of your server, or both. For more information see Microsoft Knowledge Base Q266418 at http://support.microsoft.com

This KBA is no help I do not have Outlook installed on the exchange server. This is a production server so I dont waht to try to make any changes unless I'm sure of the solution. I tried googleing for a solution with no luck. ANy info or links would be appreciated.
Thank you,

You've got 35 points available to ask this question - ugh sorry.
1 Solution
Did you install Outlook on this box? The Outlook mapi32 is diffrent from the Exchange ESM version and somtime messes things up.
quell23Author Commented:
Thanks but I do not have Outlook installed on the exchange server. Never have. Another thing I noticed is that exchange is now sending out NDR's. I have performed numerous relay test and all say no relay allowed. It is sending out NDR's from spam that has been coming in. Under internet msg formats in the adv tab nothing is checked besides Preserver senders display name. So  I have exchange configured to not send any NDR's. I have followed the instructions at http://www.amset.info/exchange/spam-cleanup.asp 

Anyway thats another problem possably another question, my main concern right now is the mapi32.dll problem.
quell23Author Commented:
UPDATE: I'm not for sure how or why this worked but it got rid of the pop up warning.
 I renamed mapi32.dll to mapi32.old  and then ran fixmapi.exe (which is supposed to be something outlook uses when there is 2 different versions present) Then rebooted the server and it works fine. No more pops up warning.  Just looked into the c:\winnt\system32 folder and there is no mapi32.dll file. There is the org one mapi32.old. Not for sure what this file is for. Back to googleing
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

quell23Author Commented:
Its only 35 points but I think my last post qualifies as a UPDATE and a fix to the problem.
Closed, 35 points refunded.
Community Support Moderator
The easiest thing is to copy the mapi32.dll from the Exchange SP2 files to the system32 directory.  This files is not registered so attempts to register it will fail.  Reinstalling Exchange is a waste of time!

Featured Post

Take Control of Web Hosting For Your Clients

As a web developer or IT admin, successfully managing multiple client accounts can be challenging. In this webinar we will look at the tools provided by Media Temple and Plesk to make managing your clients’ hosting easier.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now