Outlook 2003 Mapi32.dll is Corrupt or Wrong Version
A few days I came cross a user who reported that she was unable to launch Outlook 2003. However, all Office applications (MS Office 2000) seemed to be working fine without any errors.
The exact error message was
"Cannot start Microsoft Outlook. Mapi32.dll is corrupt or the wrong version. This could have been caused by installing other messaging software. Please reinstall Outlook."
The only change I spotted was an install of a AOL Messenger which could well have corrupted or over written the mapi32.dll.
Therefore, the first step that I carried out was to remove AOL messenger, and reinstall Office 2000 and Outlook 2003. However, this didn't rectify the issue. There weren't many system checkpoints, but nevertheless carrying out a system restore was also unsuccessful. Didn't have much luck with Microsoft's Knowledge Base.
The solution was:
Downloaded Windows Installer Clean Up Utility Remove Tool, available here, and used it to remove AOL Messenger, Microsoft Office 2000 and Microsoft Outlook 2003. Following this I reinstalled Microsoft Office 2000 and then Microsoft Outlook 2003.
This resolved the problem.
The exact error message was
"Cannot start Microsoft Outlook. Mapi32.dll is corrupt or the wrong version. This could have been caused by installing other messaging software. Please reinstall Outlook."
The only change I spotted was an install of a AOL Messenger which could well have corrupted or over written the mapi32.dll.
Therefore, the first step that I carried out was to remove AOL messenger, and reinstall Office 2000 and Outlook 2003. However, this didn't rectify the issue. There weren't many system checkpoints, but nevertheless carrying out a system restore was also unsuccessful. Didn't have much luck with Microsoft's Knowledge Base.
The solution was:
Downloaded Windows Installer Clean Up Utility Remove Tool, available here, and used it to remove AOL Messenger, Microsoft Office 2000 and Microsoft Outlook 2003. Following this I reinstalled Microsoft Office 2000 and then Microsoft Outlook 2003.
This resolved the problem.
0 Comments:
Post a Comment
<< Home