DOCUMENT:Q148272 06-AUG-2002 [exchange] TITLE :XADM: Exchange Server Setup Halts Copying MAPI32.DLL PRODUCT :Microsoft Exchange PROD/VER:winnt:4.0,5.0 OPER/SYS: KEYWORDS:kbsetup exc4 exc5 ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Exchange Server, versions 4.0, 5.0 ------------------------------------------------------------------------------- SYMPTOMS ======== The Microsoft Exchange Server Setup program may pause with a dialog box stating the following: STOP Setup cannot copy :\SETUP\\MAPI32.DLL: The file cannot be overwritten because it is in use by another process. CAUSE ===== The Microsoft Exchange Server Setup program tries to install Mapi32.dll to the \System32 directory during installation. It is possible that some mail-aware application or Microsoft Windows NT service is running that has already loaded this DLL file; therefore, the file is in use and cannot be overwritten. RESOLUTION ========== Close all running applications except for the Setup program. Stop all services that are mail-aware (capable of sending e-mail) such as anti-virus software, Compaq Insights Agents, Simple Network Management Protocol (SNMP), and so on. Click Retry. If this does not allow the Setup program to continue, or if the application or service cannot be determined at this time, click Ignore. The Setup program should finish. At this point, the application or service using Mapi32.dll must be determined and temporarily halted so that \Setup\\Mapi32.dll can be manually copied to the \System32 directory. You need to be aware of some less obvious MAPI-aware applications, specifically, some uninterruptible power supplies, include monitoring software that runs as a Windows NT service. This software may be mail-aware and configured to send e-mail to a system administrator under specific monitored conditions. STATUS ====== In Microsoft Exchange Server version 4.0, this behavior is by design and will not be changed. Microsoft has confirmed this to be an issue in Microsoft Exchange Server version 5.0. This has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): S E R V P A C K Additional query words: ====================================================================== Keywords : kbsetup exc4 exc5 Technology : kbExchangeSearch kbExchange500 kbExchange400 kbZNotKeyword2 Version : winnt:4.0,5.0 Issue type : kbbug Solution Type : kbfix ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 2002.