This article was previously published under Q258505
This article has been archived. It is offered "as is" and will no longer be updated.
If RichWin, which changes the internal language of a workstation to UTF-8 or UTF-7, is installed on your computer and you use Microsoft Outlook to log on to an Exchange Server computer, the Exchange Serverinformation store may stop unexpectedly with a stack dump that is similar to thefollowing:
This issue can occur because any query that a client submits needs to be converted first to Unicode by the information store using the software development kit (SDK) function MultiByteToWideChar(). The flag of the conversion is always set as MB_PRECOMPOSED. In this case, the properties in the query are converted from UTF-8 or UTF-7 to Unicode, which does not allow the MB_PRECOMPOSED flag to be used. Then the conversion stops with returned value as 0. The later reference to the string causes an access violation.
To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
191914 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The following files are available for download from the MicrosoftDownload Center:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.
For additional information about conversion between UTF-8 or UTF-7 and UNICODE, click the article number below to view the article in the Microsoft Knowledge Base: