Outlook 2003 and "Cached Mode"

[Alan]

We been testing our extensions / COM-Addins under Outlook 2003 and have
noticed a number of anomolies that only appear when cached mode is enabled.
Basically, we receive a lot of 'Conflict Messages' and I'm trying to
understand what is happening.

In my client extension (during OnDelivery) I delete a receipt notification
once certain criteria have been met. If I look in the deleted items folder
I see lots of 'Conflict Messages' for the deleted receipt notification.
Now, when I attempt to debug I can't immediately replicate the problem, it
appears the 'Conflict Messages' occur when Outlook resynchronises the cache,
which could be at anytime.

Therefore, it appears that during the OnDelivery I'm getting a notification
for the message arriving in the cache, I'm updating this message and then
Outlook is complaining that my modified cached message is different to the
unmodified mailbox message at the Server. (This description would seem to
fit in with some of the other problems I'm seeing!). Is this correct, Can I
get around this?

Alan.

 

[Ken Slovak - [MVP - Outlook]]

The cache is always going to be somewhat out of synch with the server
mailbox and is the local OST file. There are some anomalies with
cached mode as you have seen. One other thing to be aware of is if you
are using cached mode with Exchange 5.5 you will get a bad return
value of No Exchange when checking ExchangeConnectionMode. In that
case you have to use the old style tests for the presence of an
Exchange account to see if Exchange is there and then No Exchange
tells you that cached mode is being used.

It's already been bugged to the Outlook team and the owner of the
Outlook object model is well aware of the problem. We'll have to see
if SP1 has any fixes for the problem. In the meantime you might have
to use client-side code instead of server-side code to avoid the
problem.