DOCUMENT:Q266259 28-JUN-2001 [exchange] TITLE :XGEN: Messages Properties Do Not Save Correctly PRODUCT :Microsoft Exchange PROD/VER:winnt:5.5 OPER/SYS: KEYWORDS:exc55 kbExchange550preSP4fix kbExchange550sp4Fix kbgraphxlinkcritical kbExchange2000SP1 ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Exchange Server, version 5.5 ------------------------------------------------------------------------------- SYMPTOMS ======== If you use multiple MAPI applications to open a message in the information store, and then make changes to an attachment (such as deleting the attachment), the properties for the attachment may not be saved correctly. For example, if an antivirus program deletes the attachment and a secondary MAPI application gains access to the message at the same time, the attachment icon is not removed, even though the attachment is deleted. RESOLUTION ========== To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, please see the following article in the Microsoft Knowledge Base: Q191914 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack The following files are available for download from the Microsoft Download Center: x86: DownloadDownload Q248838engi.exe now (http://www.microsoft.com/downloads/release.asp?ReleaseID=25443) Alpha: DownloadDownload Q248838enga.exe now (http://www.microsoft.com/downloads/release.asp?ReleaseID=25444) For additional information about how to download Microsoft Support files, click the article number below to view the article in the Microsoft Knowledge Base: Q119591 How to Obtain Microsoft Support Files from Online Services Microsoft used the most current virus detection software available on the date of posting to scan this file for viruses. Once posted, the file is housed on secure servers that prevent any unauthorized changes to the file. STATUS ====== Microsoft has confirmed this to be a problem in Exchange Server Version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4. Additional query words: ====================================================================== Keywords : exc55 kbExchange550preSP4fix kbExchange550sp4Fix kbgraphxlinkcritical kbExchange2000SP1Fix Technology : kbExchangeSearch kbExchange550 kbZNotKeyword2 Version : winnt:5.5 Issue type : kbbug Solution Type : kbfix ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 2001.