When you start Microsoft Office Outlook 2007 or Microsoft Office Outlook 2003, you may receive the following error message:

Back to the top

This issue may occur if there is a file conflict with the MAPI file on your computer.

Back to the top

To resolve this issue, rename the Mapi32.dll file, and then start the Fixmapi.exe program:

1.	Click Start, and then click Search.
2.	Click All files and folders.
3.	In the All or part of the file name box, type mapi32.dll, and then click Search.
4.	When the search process is complete, right-click the Mapi32.dll file, and then click Rename.
5.	Type Mapi32.old, and then press ENTER.
6.	Click Start a new search, and then click All files and folders.
7.	In the All or part of the file name box, type fixmapi.exe, and then click Search.
8.	When the search process is complete, double-click Fixmapi.exe to start the repair process.
9.	Follow the on-screen instructions to complete the repair process.

Back to the top

The Microsoft Windows Messaging Subsystem (WMS) installs the core MAPI files in the C:\Windows\System folder, and earlier versions of Outlook access the files from that location. Simple MAPI programs, such as Microsoft Outlook Express, Eudora, Netscape, and other third-party programs install and access the Mapi32.dll file. You can use programs that support simple MAPI to send documents by clicking Send To on the File menu.

Note This issue may affect programs such as the Exchange System Manager, even if the Exchange Server is not on the same computer as the Exchange System Manager. The issue occurs after you run the Fixmapi.exe program. If you replace the MAPI file with the Outlook MAPI file, Exchange System Manager may not work anymore. Also, if you do not replace the file, Outlook may not work correctly. This error occurs each time you start Outlook until you replace the file with the Outlook MAPI file, but this action breaks Exchange System Manager. Because of this, Microsoft recommends that you do not have Outlook 2000 or earlier on the same computer as Exchange System Manager or Exchange server. To avoid this scenario, use Outlook Web Access or a Terminal Server session to access e-mail messages.

Back to the top