The information in this article applies to:
SYMPTOMSThe MAPI API IMessage::Savechanges() may fail with a MAPI_E_NOT_FOUND error when saving a message with custom properties whose property ranges are in the allowable ranges defined by the MAPI spec (0x6800 - 0x7FF). STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. MORE INFORMATION
This can occur when you attemp to "overload" property IDs by using several of the same property tag IDs with differing types. The Micrososft Information Store will not allow more than a single type per property tag in a single folder. Additional query words:
Keywords : |
Last Reviewed: January 15, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |