This article was previously published under Q303911
This article has been archived. It is offered "as is" and will no longer be updated.
If you install Microsoft Data Access Components version 2.6 on an Exchange 2000 server, double-byte character set (DBCS) characters in the subject, location, and body part of a reply of meeting request may not display correctly when you use Microsoft Outlook Web Access (OWA) or Collaboration Data Objects (CDO).
In Exchange 2000, the vCalendar stream in the appointment is encoded with UTF-8. This problem can occur because after Microsoft Data Access Components 2.6 is installed on the Exchange 2000 server, the ActiveX Data Objects (ADO) Stream object uses code page 28591 for ISO-8859-1; Microsoft Data Access Components 2.5 uses code page 1251. This causes the DBCS characters to display incorrectly.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The version of this fix should have the following file attributes or later:
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 1.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.