…Recently, I worked with a customer who was facing the problem described below. We requested a fix but ended up finding a workaround using a Transport Agent. At this time there is no plan to fix this issue in Exchange 2007…
In an OnSyncSave store event in Exchange 2007 every field's value of a plain text message which triggers the event returns the following exception in the first pre-commit event:
"Operation failed to complete and the status is unavailable. The field may be unavailable or the operation was not attempted."
When the OnSyncSave event fires again for this message after the message has been committed to the store the property values can be read.
NOTE: HTML and RTF messages do not have this problem - this only applies to Plain Text messages.
There are no straight forward workarounds, only other options which may or may not suit your application’s needs:
Again, depending on your solution one of these workarounds or combination of two might accomplish what you need. An example of combining two of these options would be to use a transport agent to tag messages as they are sent to a particular mailbox and then use a rule to key off this tag and move those messages to a specific folder on deliver.
Microsoft Exchange Server 2007 performance tutorial Securing your Exchange Server 2007 journaling archives