XCCC: Mail Clients That Are Not UTF-8 Aware Cannot View Messages Sent from Exchange 2000 (273615)



The information in this article applies to:

  • Microsoft Exchange 2000 Server

This article was previously published under Q273615

SYMPTOMS

When users use Microsoft Internet Explorer 5 or later to gain access to Microsoft Outlook Web Access (OWA) and send a message, recipients who have mail clients that are not Unicode Translation Format-8 (UTF-8) aware cannot view the message.

WORKAROUND

To work around this problem, turn the feature to use regional characters on.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To turn the feature to use regional characters on:
  1. Click Start, point to Settings, and then click Control Panel.
  2. Stop the MSExchangeIS service.
  3. Stop the W3SVC service.
  4. Click Start, and then click Run.
  5. In the Open box, type regedit.
  6. Locate the following key in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWEB
    \OWA\UseRegionalCharset

  7. On the Edit menu, click Modify.
  8. In the Value Data box, type 1, and then click Exit.
  9. On the Registry menu, click Exit.
  10. Restart the MSExchangeIS service.
  11. Restart the W3SVC service.
Note If the registry key does not exist on the server, you can create it. To create the registry key, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following key in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWEB\OWA

  3. Click Edit, click Add Value, and then type the following information in the Value box and in the REG_DWORD Data box:

    Value: UseRegionalCharset
    REG_DWORD Data: 1
  4. Click OK, and then quit Registry Editor.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

Modification Type:MajorLast Reviewed:12/19/2003
Keywords:kbbug kbExchange2000preSP1fix kbfix kbgraphxlinkcritical kbQFE KB273615