DOCUMENT:Q153755 31-MAR-1999 [exchange] TITLE :XCLN: Mac Err Msg: Microsoft Exchange Could not be Started PRODUCT :Microsoft Exchange PROD/VER:WINDOWS:4.0,5.0 OPER/SYS: KEYWORDS:kbusage ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Exchange Macintosh client, versions 4.0, 5.0 ------------------------------------------------------------------------------- SUMMARY ======= The Microsoft Exchange Macintosh client requires that the Windows NT Macintosh Codepage support be installed on the Microsoft Exchange Server. SYMPTOMS ======== You see the following errors in the Windows NT Event Log on the Microsoft Exchange Server: Event ID = 10012, Source = MacFile, "The File Server for Macintosh service failed to start because a critical error occurred while trying to initialize the AppleTalk Filing Protocol driver (SfmSrv.sys) with server parameters." Event ID = 7024, Source = Service Control Manager, "The File Server for Macintosh service terminated with service specific error 2." You will see the following errors when you attempt to start the Microsoft Exchange Macintosh client: Microsoft Exchange could not be started. The Microsoft Exchange Server computer is not configured to support your codepage. Contact your system administrator. Microsoft Exchange could not be started. The action could not be completed. RESOLUTION ========== 1. Start the Windows NT Registry Editor, Regedt32.exe, on the Microsoft Exchange Server and locate the following key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Nls\Codepage 2. From the Edit menu, click Add Value. 3. Enter a value name of 10000, set the data type to REG_SZ, click OK, set String to c_10000.nls, and click OK. 4. Exit the Registry Editor. 5. Verify that the C_10000.nls file is located in the \system32 directory. MORE INFORMATION ================ The Macintosh codepage (10000) is normally loaded during the installation of Windows NT. The SFM services are not required for a Microsoft Exchange Macintosh client to connect using the TCP/IP protocol stack. For additional information, please see the following articles in the Microsoft Knowledge Base: Q102987 REG: CurrentControlSet, PART 1 Q102996 REG: Network Services Entries, Part 2 Additional query words: code page XADM ====================================================================== Keywords : kbusage Technology : kbHWMAC kbOSMAC kbExchangeSearch kbExchangeClientSearch kbExchange500Mac kbExchange400Mac Version : WINDOWS:4.0,5.0 ============================================================================= 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 1999.