This article was previously published under Q248825
This article has been archived. It is offered "as is" and will no longer be updated.
When you send a message through an Exchange Server computer, the message is delivered successfully, but when the recipient views the message in an e-mail client, the Subject field is not displayed correctly.
This issue occurs when the Subject field is separated into multiple lines, causing it to be parsed incorrectly by the information store.
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:
191014 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.
NOTE: When you start this version of the information store, the information store databases are automatically upgraded to a new format. After the databases have been upgraded, you can restore an earlier version of the Store.exe file on the server, but only if it is version 5.5.2651.32 or later. If you restore a Store.exe file earlier than version 5.5.2651.32 after the database has been upgraded, you are no longer able to start the information store. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
244976 XADM: Event ID 1197 and 1005 When Starting the Information Store
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.