XCLN: ErrMsg "An extension failed to initialize..."

 Last reviewed: May 8, 1997
Article ID: Q157822

The information in this article applies to:
  • Microsoft Exchange Windows NT client, version 4.0

SUMMARY

When you attempt to start the Microsoft Exchange Windows NT client with the Exchange Server and Microsoft Mail services running, you may receive the following error message 

   An extension failed to initialize. The extension entry contains invalid
   parameters.

   <extension>
where <extension> is an MS Mail 3.x extension such as "0;;;;;;;;;;".

CAUSE

There is an Msmail.ini file in the Winroot directory. WINROOT is the directory which Windows NT Workstation or Windows NT Server was installed.

RESOLUTION

To resolve this problem:

  • Rename the \WINROOT\MSMAIL.INI file to *.OLD.

-OR-
  • Remark out the invalid entry or entries referenced in the error message
by placing a semicolon at the beginning of the line. The invalid entry or entries may be located in one (or more) of the following sections of the Msmail.ini file: 

   [Custom Commands]
   [Custom Menus]
   [Custom Messages]

MORE INFORMATION

The Microsoft Mail service for the Microsoft Exchange client checks for and uses entries in the MSMAIL.INI file.

For additional information about how Exchange clients use the Msmail.ini, please see the following article in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q141272
   TITLE     : XCLN Win: How Exchange Clients Use MSMAIL.INI and SHARED.INI

Additional query words: sfs pcmail
Keywords : kbusage XCLN
Version : 4.0
Platform : WinNT

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