Hello,
Since this week Microsoft updates, Outlook (2010/2016) can't open archived/stored items. Maybe, Outlook is blocking VBScript of custom forms. I'm using EV Client 10/11.
To view an email, the users must "restore" to the mailbox and then open it.
The message is: This item has been archived by Enterprise Vault. Click here to view the original item (this link doesn't work).
Thank you.
The following registry script is all in one for outlook 2010, 2013 and 2016, either for win32 or win64 operation system. This way it can be easily distributed via GPO (without the hassle of filtering for different combinations of OS and Outlook). Once this registry script is executed the archived items can be opened by doubleclick in Outlook.
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Outlook\Forms\TrustedFormScriptList] "IPM.Note.EnterpriseVault.PendingArchive"="" "IPM.Note.EnterpriseVault.PendingArchive.ArchiveMe"="" "IPM.Note.EnterpriseVault.Shortcut.DeleteMe"="" "IPM.Note.EnterpriseVault.Shortcut.RestoreMe"="" "IPM.Note.EnterpriseVault.Shortcut"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Outlook\Security] "DisableCustomFormItemScript"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\14.0\Outlook\Forms\TrustedFormScriptList] "IPM.Note.EnterpriseVault.PendingArchive"="" "IPM.Note.EnterpriseVault.PendingArchive.ArchiveMe"="" "IPM.Note.EnterpriseVault.Shortcut.DeleteMe"="" "IPM.Note.EnterpriseVault.Shortcut.RestoreMe"="" "IPM.Note.EnterpriseVault.Shortcut"="" [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\14.0\Outlook\Security] "DisableCustomFormItemScript"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\15.0\Outlook\Forms\TrustedFormScriptList] "IPM.Note.EnterpriseVault.PendingArchive"="" "IPM.Note.EnterpriseVault.PendingArchive.ArchiveMe"="" "IPM.Note.EnterpriseVault.Shortcut.DeleteMe"="" "IPM.Note.EnterpriseVault.Shortcut.RestoreMe"="" "IPM.Note.EnterpriseVault.Shortcut"="" [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\15.0\Outlook\Security] "DisableCustomFormItemScript"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Outlook\Forms\TrustedFormScriptList] "IPM.Note.EnterpriseVault.PendingArchive"="" "IPM.Note.EnterpriseVault.PendingArchive.ArchiveMe"="" "IPM.Note.EnterpriseVault.Shortcut.DeleteMe"="" "IPM.Note.EnterpriseVault.Shortcut.RestoreMe"="" "IPM.Note.EnterpriseVault.Shortcut"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Outlook\Security] "DisableCustomFormItemScript"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\16.0\Outlook\Forms\TrustedFormScriptList] "IPM.Note.EnterpriseVault.PendingArchive"="" "IPM.Note.EnterpriseVault.PendingArchive.ArchiveMe"="" "IPM.Note.EnterpriseVault.Shortcut.DeleteMe"="" "IPM.Note.EnterpriseVault.Shortcut.RestoreMe"="" "IPM.Note.EnterpriseVault.Shortcut"="" [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\16.0\Outlook\Security] "DisableCustomFormItemScript"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Outlook\Forms\TrustedFormScriptList] "IPM.Note.EnterpriseVault.PendingArchive"="" "IPM.Note.EnterpriseVault.PendingArchive.ArchiveMe"="" "IPM.Note.EnterpriseVault.Shortcut.DeleteMe"="" "IPM.Note.EnterpriseVault.Shortcut.RestoreMe"="" "IPM.Note.EnterpriseVault.Shortcut"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Outlook\Security] "DisableCustomFormItemScript"=dword:00000000
Trace, this is great. Just need to add 2007 and we are good. This worked well for me, thanks.
Has anyone had success getting Outlook 2007 to work yet?
I merged all the registry settings in a single .reg, just as you did, and then used the RegtoXML.ps1 script to create a GPP.
Didn't know that this issue was public. I came here just to post the issue and solution i came up with.
Today i encountered this issue in a customer running 11.0.1, Outook 2013 x64 on 64 bits OS. Initially i was looking in different directions since they had a lot of changed in their infrastructure in the past month but after discarding other factors i suspected it was related to Outlook scripting functionality.
After creating the following keys the user can retrieve the original email:
REG_SZ
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Outlook\Forms\TrustedFormScriptList]
"IPM.Note.EnterpriseVault.Shortcut"=""
DWORD
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Outlook\Security]
"DisableCustomFormItemScript"=dword:00000000
The location of the registry keys shall respect the Outlook/Office bitness. Use the WOW6432Node folders if 32 bit.
This worked for me. I have tested it on Outlook 2010 and Outlook 2016. Both 32-bit version.
These are the registry keys for 32-bit Office:
Windows Registry Editor Version 5.00
;Outlook 2007
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\12.0\Outlook\Forms\TrustedFormScriptList]
"IPM.Note.EnterpriseVault.Shortcut"=""
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\12.0\Outlook\Security]
"DisableCustomFormItemScript"=dword:00000000
;Outlook 2010
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\14.0\Outlook\Forms\TrustedFormScriptList]
"IPM.Note.EnterpriseVault.Shortcut"=""
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\14.0\Outlook\Security]
"DisableCustomFormItemScript"=dword:00000000
;Outlook 2013
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\15.0\Outlook\Forms\TrustedFormScriptList]
"IPM.Note.EnterpriseVault.Shortcut"=""
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\15.0\Outlook\Security]
"DisableCustomFormItemScript"=dword:00000000
;Outlook 2016
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\16.0\Outlook\Forms\TrustedFormScriptList]
"IPM.Note.EnterpriseVault.Shortcut"=""
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\16.0\Outlook\Security]
"DisableCustomFormItemScript"=dword:00000000
Great find Ricardo, thanks for sharing
Thanks for sharing. We are also seeing more and more customers facing this problem.
I have opened case number 22323941.
We too are experiencing the same error since Microsoft Updates yesterday.
I advise to open a case at Veritas for this.
They should be able to pinpoint where the issue comes from. They should be able to hopefully find a workaround, and escalate to MS to get an explanation for the issue, and hopefully a fix.
Hello,
we have a same issuse
Ronen
