XCLN: Err Msg: Spell Check Operation could not be Completed

 Last reviewed: November 7, 1997
Article ID: Q164156
The information in this article applies to:
  • Microsoft Exchange Windows 3.x client, versions 4.0 and 5.0
  • Microsoft Exchange Windows 95 client, versions 4.0 and 5.0
  • Microsoft Exchange Windows NT client, versions 4.0 and 5.0

SUMMARY

When spell checking a message within a Microsoft Exchange Windows client, the following error may be displayed 

   The spelling operation could not be completed. The spelling
   checker could not be started. Some components are either missing
   or incorrectly configured in your Win.ini file. See your
   administrator.
This error is usually due to the Microsoft Exchange Client looking for spelling files in either an invalid directory or a location that you don't have permission to access. Confirm the following registry entries and Win.ini entries point to valid files stored in accessible locations.

For Windows NT and Windows 95 clients: 

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Proofing Tools
   \Spelling\1033\Normal

   Engine=C:\Program Files\Common Files\Microsoft Shared\PROOF\MSSP232.DLL

   Dictionary=C:\Program Files\Common Files\Microsoft Shared\PROOF\mssp2_en.lex
For Windows 3.x clients: 

   [MS Proofing Tools]
   Custom Dict=C:\win31\msapps\proof\CUSTOM.DIC
   Spelling 1033,0=c:\win31\msapps\proof\msspell.dll,
      c:\win31\msapps\proof\mssp_am.lex
   Spelling (Mail) 1033,0=C:\WIN31\MSAPPS\PROOF\MSSPELL.DLL,
      C:\WIN31\MSAPPS\PROOF\MSSP_AM.LEX

Additional query words:
Keywords : XCLN kberrmsg kberrmsg
Version : 4.0 5.0
Platform : WINDOWS
Issue type : kberrmsg
Solution Type : kbworkaround

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: November 7, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.