XCLN: Mac Err Msg: Microsoft Exchange Could not be StartedLast reviewed: April 3, 1997Article ID: Q153755 |
The information in this article applies to:
SUMMARYThe Microsoft Exchange Macintosh client requires that the Windows NT Macintosh Codepage support be installed on the Microsoft Exchange Server.
SYMPTOMSYou 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
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Nls\Codepage 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 <Windows NT install folder>\system32 directory. MORE INFORMATIONThe 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:
ARTICLE-ID:Q102987 TITLE :REG: CurrentControlSet, PART 1 ARTICLE-ID:Q102996 TITLE :REG: Network Services Entries, Part 2 |
Additional query words: code page XADM
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |