XCLN: Unable to Copy Mssp2_en.lex During Client Setup

Last reviewed: August 6, 1997
Article ID: Q151208
The information in this article applies to:
  • Microsoft Exchange Windows 95 client, versions 4.0 and 5.0

SUMMARY

When you attempting an Exchange client setup on a computer that is using a shared copy of Office 95, the following error message may be encountered:

   Unable to copy mssp2_en.lex the file is currently in use.

MORE INFORMATION

Exchange does share a copy of this file with Office95. If the share where this is located, or the file itself, is marked read-only, the above error message will occur during the client setup.

RESOLUTION

To get around this error message make sure the file is not marked read- only, and if the file is on NTFS, change the permissions to Change for everyone and rerun setup.

This solution will not work if any user has the .LEX file open. An alternate solution using either the Microsoft Exchange Setup Editor or Custom Setup, is to deselect Spelling as an option. This will not attempt to install spelling, but spell checking will still be an option on Windows NT or Windows 95 clients, because the registry entries still point to the shared directories on the Server. Spell checking will be available but will use the older .LEX file for spell checking.


Additional query words:
Keywords : XCLN kbsetup
Version : 4.0
Platform : WINDOWS
Issue type : kbprb


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.

Last reviewed: August 6, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.