XADM: Message Using Non-GAPI Code Page Is Not Converted Properly (232600)
The information in this article applies to:
- Microsoft Exchange Server 5.5
This article was previously published under Q232600 SYMPTOMS
If you compose a message using a GAPI code page, and then send the message through an Exchange Server computer, the information store may not properly convert the message to the appropriate format. As a result, the message is not sent successfully.
CAUSE
This problem occurs when the information store attempts to convert the GAPI code page to a non-GAPI code page. The information store attempts to start a GAPI conversion process, even though it has already specified that the outbound message is using a non-GAPI code page.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
191014 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The English version of this fix should have the following file attributes or later:
Component: Information Store
|
Gapi32.dll | 5.5.2620.0 | Mdbmsg.dll | 5.5.2620.0 | Netif.dll | 5.5.2620.0 | Store.exe | 5.5.2620.0 |
STATUSMicrosoft 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 3.
Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
---|
Keywords: | kbHotfixServer kbQFE EXC55SP3Fix kbbug kbfix KB232600 |
---|
|