Vault 7.0 SP1 and Outlook 2007

Brian Spooner's picture

Ok, so Vault 7.0 SP1 is finally out and we now have official support for IE7, Exchange Server 2007 and Outlook 2007.

However, there's a caveat in the 7.0 SP1 readme and no resolution.
Quoting from this doc:
http://support.veritas.com/docs/287443

"There is an issue whereby the Enterprise Vault Outlook add-in may become disabled when using the Enterprise Vault client with Outlook 2007. This is most likely to occur when Exchange System Manager and Outlook 2007 are installed on the same workstation. "

Anyone know of a fix? I'm our Exchange and Vault admin so I'd really like to keep the Exchange tools installed on my PC. Everytime I open Outlook 2007 with 7.0 SP1 user extensions installed I'm still getting the error about valkyrie.dll being disabled.

Thanks,
-Brian

Micah Wyenn's picture

I dunno...here's a stupid guess tho...try um, putting an older version of the mapsvc.inf in the c:\windows\system32 ?

This prolly won't work, but at least it'll distract you long enough for someone who knows what they're talking about to answer. :)

micahMessage was edited by:
Micah Wyenn

EV Director's picture

Hi,

I guess I'm that person then Micah since I got that added to the release notes :-)

You can try a few things on the affected PC.
1. run fixmapi and see if that resolves it
2. uninstall ESM and reinstall and see if that resolves it
3. After step 2 above run fixmapi

I know people who've been fine with ESM and Outlook 2007 and EV, and others who have not been ok and had to follow the steps above.

Like I say problem is it is unsupported (ESM and Outlook) and so difficult to troubleshoot.
More than happy to hear back if the above steps resolved it.

Mike B

Brian Spooner's picture

Thank you very much, that did the trick!

EV Director's picture

Hi,

Great news...but which bit
just run fixmapi or uninstlal, reinstall and fixmapi?

Mike B

Jeremy Roberts's picture

Using V6 sp4 if I unistall ESM and install the Client it works then fails as soon as I reinstall ESM 2003.
Why is this an unsupported configuration? EV admins are very likely to be Exchange Admins as well I would have thought, especially outside of the US where specialism is not the norm.

Brian Spooner's picture

I had to uninstall ESM, reinstall vault extensions...tested it at this point and it worked. Re-installed ESM, tested it and verified it broke. Ran fixmapi and it worked again.

I hope they consider supporting this configuration in the future. I'm sure many EV Admins are also Exchange admins and have the tools loaded on their workstations.

At least we have a workaround for now though....thanks again for your help.

Jeremy Roberts's picture

Install client software, uninstall ESM, install ESM and run fixmapi procedure did work in the end for me. I have upgraded from version 6 to 7 and it is working as well.

TonySterling's picture

Jeremy,
The ESM and OL configuration is from Microsoft, not Enterprise Vault.

Glad you got it all working. :)

Cheers,

Tony Sterling
bluesource

David standish's picture

FYI: This has been a long time best practice from Microsoft. See http://support.microsoft.com/kb/266418/en-us.

If you can get it to work great, but it may break again when you have hotfixes/service packs/upgrades that need to be installed for either Outlook, Exchange, or new versions of the user extensions.