In Microsoft Exchange Server 5.0 and in Microsoft Exchange Server 5.5, the national language support (NLS) files are copied to the Exchange server when you run the Setup program on the Exchange server. The NLS files are copied to support IMAIL and to support access to the Exchange directory by localized MAPI clients. For language support in Exchange Server 4.
x, you had to manually copy files, register the files, and then add the Exchsrvr.inf file from the Langpack folder on the Microsoft Windows NT Server 4.0 CD-ROM.
Note The IMAIL sub-component of the Microsoft Exchange Information Store service (Store.exe) performs content conversion to convert an e-mail message from Microsoft Database Format (MDBEF) to Simple Mail Transfer Protocol (SMTP) MIME format or to UUencode format.
This behavior is different in Exchange 2000 Server and in Exchange Server 2003. Because Exchange 2000 Server and Exchange Server 2003 require the implementation of the Windows 2000 Active Directory directory service, Exchange name registration is done through a global catalog server. When you run the Setup program for Windows 2000 Server, the NLS files are copied and registered. However, the NLS files that are installed may vary depending on the language locales that the administrator installs.
By default, not all language locales are installed. This behavior is not an issue in IMAIL. However, when you try to resolve names while you are creating MAPI profiles by using a localized MAPI client, you may experience the problem that is mentioned in the "Symptoms" section.
If you receive an error message that is similar to the error message that is mentioned in the "Symptoms" section, and the global catalog server does not meet the conditions that are mentioned in the "Cause" section, click the following article number to view the article in the Microsoft Knowledge Base:
297801�
Troubleshooting Check Name errors