A non-Exchange Server MAPI subsystem is installed
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool queries the CIM_Datafile Microsoft Windows® Management Instrumentation (WMI) class to determine the version of MAPI32.dll that is in the two following folders:
If the same version and copy of MAPI32.dll is not found in both folders, an error is displayed.
To ensure that a single version of the MAPI is in use, Exchange Server Setup copies MAPI32.dll to both the <drive>:\Program Files\Exchsrvr\Bin and %Systemroot%\system32 directories. If another MAPI application, such as Microsoft Office Outlook® 2003 or a third-party program is installed on the Exchange Server computer, it may copy a different version of MAPI32.dll into the System32 folder and potentially break Exchange functionality. These issues occur because versions of these two products produce a conflict of the MAPI subsystem that may not be cleanly reconciled without breaking either Exchange Server or the other MAPI application.
It is strongly recommended that you not install Outlook 2000 or a later version of Outlook, and Exchange Server 2003, Exchange 2000 Server or Exchange Server 5.5 on the same computer.
A common reason to want to install Outlook on the same computer with Exchange Server is to take advantage of certain Outlook components in server-side programs. For most program development requirements, Outlook is not required on an Exchange computer. Exchange Server includes Collaboration Data Objects (CDO), which can provide functionality that is similar to the Outlook object model. CDO is designed for server-side use and also avoids the implications that are included in later versions of Outlook. For more information, see the Microsoft Knowledge Base article 290500, "OL2002: Developer Information About E-Mail Security Features" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=290500).
Another common reason is the requirement to create MAPI profiles. Exchange Server includes all the functionality needed to create MAPI profiles and does not require Outlook for any reason. For more information about how to create MAPI profiles without installing Outlook, see the Knowledge Base article 306962, "HOWTO: Create MAPI Profiles Without Installing Outlook" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=306962).
If you have to install Outlook and Exchange Server on the same computer for demonstration purposes, it is recommended that you use one of the following configurations, which have been tested for demonstration purposes:
Exchange 2000 Server used with Outlook 2000
Exchange 2000 Server used with Outlook 2002
To correct this error
Uninstall Microsoft Outlook or the third-party MAPI application from the Exchange server.
Rerun Exchange Server Setup, and click Reinstall.
For more information about using Microsoft Office Outlook 2003 and Microsoft Exchange Server on the same computer, see the Microsoft Knowledge Base article 266418, " XCCC: Microsoft Does Not Recommend Installing Exchange 2000 Server and Outlook 2000 or Later on the Same Computer" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=266418).
For more information about resolving MAPI conflicts, see the Knowledge Base article 229700, "HOWTO: Find the Correct Path to MAPISVC.INF Under Outlook 2000" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=229700).
For more information about the MAPI32 stub library, see Messaging API (MAPI) (http://go.microsoft.com/fwlink/?linkid=34395).