XADM: Message Is Never Delivered to Foreign System User

When you attempt to send a message to a foreign system user through an Exchange Server computer that is low on memory, the message may never be delivered. This issue occurs independent of the connector through which the message must be delivered, but may occur with the following connectors:

• Internet Mail Service
• Exchange Connector for Lotus cc:Mail
• Exchange Notes Connector, Exchange SNADS Connector, or Exchange PROFS Connector
• Exchange Connector for Novell GroupWise

This issue occurs when the information store allocates memory incorrectly while processing the message. As a result, the message is never sent through the appropriate connector so it can be delivered to the foreign system user.

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 the Microsoft Knowledge Base: The following files are available for download from the Microsoft Download 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: 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:

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.