Unable to reply/forward to a shortcut while working offline in Outlook 2010

[FabioC]

Hi,

I'm having an issue with my users when they work offline in Outlook (i.e. without being connected to company network).

I'm able to reproduce the issue on my station, by unpluging the network cable.

When they try to reply or forward to a shortcut, the mail open but not in reply/forward mode. And it only show an error like he's trying, and failling, to retrieve the item from the vault instead of just put the shortcut body in a reply/forward message.

Here's a pic of the issue :

Some details of the setup:

- Outlook 2010

- Enterprise Vault Client 9.0.2.1061.0 (http add-in)

- Enterprise Vault 9.0.2

Error that shows up in the client log : CShortcutItem::Display...Return Last Failed error: 0x80004005

If someone has an idea, that would be great :)

[JesusWept3 · Accepted solution]

Huh that is weird, it is weird; would suggest contacting symc support and logging a defect, however it would be treated as very low priority to be honest

[SHI-CRO]

Do you have vault cache enabled?

[FabioC]

@Jesuswept2 Hope I won't have to do this :\

@Shi-Cro : No, we don't.

Thanks.

[JesusWept3]

You're gonna have to mate, they won't produce a fix without customer demand and even then they will still question the usefulness and frequency of someone replying/forwarding a message when offline

[Paul_Grimshaw]

It works OK on my 9.0.2 with Outlook 2010 and just has the shortcut in the body. What do you have th e desktop policy setting called Forward Original item? I have it set to shortcut and if I change it to original I also get the same behaviour as you have outlined in your screenshot which would be expected as it is trying to download the item and obviously cannot as it is offline. When you click on the grey banner do you get the message that the Server name could not be resolved?

[Rob_Wilcox1]

I agree with Paul and JW2.  I also can reproduce it.  

If you have the item in Vault Cache, it works.

So..  granted it would be *better* if it brought up the shortcut instead, or told you something "nicer" than the error message it gives.

Two choices.

a/ Contact Support formally.

b/ I'll raise a bug but it won't get a high priority as there is no customer weight behind it.