Article ID: 232600 - Last Review: October 28, 2006 - Revision: 3.3

XADM: Message Using Non-GAPI Code Page Is Not Converted Properly

This article was previously published under Q232600
Expand all | Collapse all

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.

RESOLUTION

To 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  (http://support.microsoft.com/kb/191014/EN-US/ ) 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

Collapse this tableExpand this table
File nameVersion
Gapi32.dll5.5.2620.0
Mdbmsg.dll5.5.2620.0
Netif.dll5.5.2620.0
Store.exe5.5.2620.0

STATUS

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 3.

APPLIES TO
  • Microsoft Exchange Server 5.5 Standard Edition
Keywords: 
kbhotfixserver kbqfe kbbug kbfix KB232600
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
 

Article Translations