MAPI32.dll problems

J

JimB

I appear to have similar problems as others who have attempted to load
Outlook 2007. After apparently successfully (???) loading Office 2007 beta,
I could not start Outlook. I uninstalled 2007, and re-installed 2003 Office
Pro. I received the error message "Cannot start Microsoft Office Outlook.
MAPI32.DLL is corrupt or the wrong version. This could have been caused by
installing other messaging software. Please reinstall Outlook."

I reinstalled outlook with the same results.
I renamed MAPI32.dll as MAPI32.old and ran fixmapi.exe. No luck

Can anyone supply any other suggestions? I am out of luck and I cannot
access my calendar or messages.
 
B

BillR [MVP]

See if renaming mapi32.dll to mapi32.old and reinstall or repair helps. You
might find various version and locations of mapi32.dll on the system.
 
J

Jimmy_Cullen

JimB I am having the exact same trouble as you:

# Installed Office 2007 Beta over Office 2003 Pro
# Uninstalled Office 2007
# Reinstalled Office 2003 Pro
# When trying to open Outlook get error message "Cannot start Microsoft
Office Outlook. MAPI32.DLL is corrupt or the wrong version. This could have
been caused by installing other messaging software. Please reinstall
Outlook."
# Have unistalled and reinstalled Outlook.
# Have renamed mapi32.dll and run fixmapi.exe
# Have copied the mapi.dll from another machine using exactly the same
software

No matter what I have tried I have not been able to get Outlook to work.
Would appreciate some help if possible!!!

Cheers,

Jimmy
 
D

DSPTurtle

I am experiencing the exact same thing. I did a global search for mapi32 and
deleted all of them and ran the fixmapi and everything else in the knowledge
base. I have uninstalled and reinstalled Office Pro 2003 twice after I
uninstalled Office 2007 Beta. I am starting to wonder if I am ever going to
be able to get Outlook back up an running. Hopefully someone has an answer
to my nightmare.
Thanks
JB
 
A

Achim Bossler

I fixed this problem by 1) unistall desktop search and 2) reinstall Office Pro
--
Achim Bossler
Open System Network AG
www.osn.ch
 
D

DSPTurtle

That did not work for me... but what did end up working for me was:
1. Uninstalled Office 2007
1. Global Search for mapi32.dll.
2. Deleted them all. Ran "fixmapi"
3. Installed MSOffice 2003
4. Rebooted
5. Uninstalled MSOffice 2003
6. Rebooted
7. Uninstalled Outlook Business Contact Manager
8. Rebooted
9. Installed MSOffice 2003
10. Rebooted
11. Ran Windows Update
12. Rebooted

So far it seems to have fixed the problem. Outlook is slow right now but I
assume it is doing its indexing.

Good Luck
 
K

Ken

Howdy-

Rename the MSMAPI32.dll file to MSMAPI32.xxx and restart outlook (I tried
renaming the mapi32.dll file all day long, and it still would not work).
Renaming MSMAPI32.dll is the only way I could get outlook 2003 to start
again. I made the mistake of uninstalling outlook 2007 because I could not
get the desktop search to install, so I uninstalled 2007 hoping my 2003
outlook would work. Big mistake.
 
I

Ivan

Had the same issues with the MAPI32.dll file. I never installed the desktop
search, which probably saved me. Initially I uninstalled and reinstalled
Office 2007 and got Outlook running again. But the next time I opened Outlook
the same thing happend. So, I uninstalled Office 2007, deleted the MAPI32.dll
files and reinstalled Office 2003 and that worked for me

One question I do have is that when installing Office 2007, it did not
upgrade Office 2003, I still had both suites on my PC. Has anyone else had
this issue?
 
K

keithg

I got around the problem just by deleting the MSMAPI32.dll in Program
Files\Common Files\System\MSMAPI\1033 and then restarting OL2003.

It went through a brief 'Installing software' routine and replaced the
file and then restarted.

Keith
 
B

borains

keithg said:
I got around the problem just by deleting the MSMAPI32.dll in Program
Files\Common Files\System\MSMAPI\1033 and then restarting OL2003.

It went through a brief 'Installing software' routine and replaced the
file and then restarted.

Keith


This did the trick for me!
I've been screwing with this for days! I can't tell you how much you
guys help by making these posts.
One thing I did have to do was to delete the file in "safe" mode
(uninstalled Desktop Search first).
M$ really needs to put something up on the knowledge base about this...

Thanks again!!
 
J

Jerry

I am having the same problem all or most of these posts are about. Downloaded
Beta and had problems so I uninstalled it. When I tried to go back to Office
Standard 2003 I got the Error message. I am without Outlook and I need it. I
have tried renaming MAPI32.DLL to MAPI32.old and it did not work for me. I
tried to delete the MSMAPI32.DLL and wasn't allowed to...access denied.
Any other solutions would be greatly appreciated to say the least.
HELP!
 
J

Jerry

Just a note to let those of you know who may not already know. When you
download Beta 7 and start through the customized installation, if you select
to NOT remove old office files, in the bottom of the dialog box it tells you
that Outlook must be removed for Bets 7. Also, I had not downloaded and
applied all of the Office Service Packs and the the new viewers, etc. I
reinstalled Beta 7 after doing all of the updates and now have Outlook back
in Beta 7. It's better than nothing I guess.
 
D

Dougl Bisset

I tried deletingt the MAPI32.dll and then tried to delete Business Contact
Manager in safe mode and Outlook still wants to open BCM.

Oh.yes, Windows Live One Care also will not open.
 
Z

zenjoe

Thanks You
changed .DLL to .OLD
reinstalled office 03, outlook works after many days of hair pulling and
thinking i had lost my calendar
joe collins
 
C

Churms

Never used a news group before, but having just, well a week ago, loaded
Office 2003 for the first time, had this Mapi32.dll problem. Like others have
been frustrated that KB wouldn't produce a solution, hence following your
advice. As a precaution (I am old and not a teckie!!) saved MSMapi32.dll to a
removeable drive. Couldn't then delete MSMapi.dll but was able to rename it
to old and then restarted OL2003. IT worked!!!!!!! Many thanks to you all who
provided the solution, but why not MS?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top