10-22-2013 11:52 AM
EV Client is 10.0.3
Outlook 2010
Exchange 2007 environment.
I've run into an issue where one of my users can't access his virtual vault. When looking at the Sync dialogue, I'm getting a "Synchronization failed" error in the header sync field. The users Virtual Vault isnt listed on the VV tab, and a "No virtual vault" error occurs during synchornization. I've run out of ideas outside of having to completely recreate the users windows profile, or do a full system re-image.Any help would be greatly appreciated.
-User has both of the neccesary PSTDisableGrow and PSTDisableGrowAllowAuthenticodeOverrides registration entires in both 12.0 and 14.0 Office keys of the registery.
-I've renamed the MDC file, which has worked in the past the handful of times Ive encountered this issue (including once before with this specific user), but this time it is not working.
-I've done partial and full resets of the cache with no luck.
-I've completely deleted the folder containing the .mdc in an attempt to rebuild, with no luck.
-I've tried uninstalling and reinstalling
-I've used the resetEVclient.exe tool with no luck
-The sync seems to fail once the .mdc reaches a specific size each time I've attempted to remake the mdc file (66,233 kb).
-I've set up the users mail profile on another system for testing, and it's loading and synching just fine on that system.
Here is an error log that I captured after a cache reset:
10-22-2013 12:00 PM
10-22-2013 02:07 PM
Hi Justin,
If you have already created the user's mail profile on another system and VC/VV is working just fine, it appears to be something related with the user's profile. I would recreate the Windows profile in the user's machine and try to synch Vault Cache again.
I hope this helps.
10-23-2013 07:36 AM
Hi,
One of the two options may suffice as a workaround.
If possible then try to ZAP the user and then try to Synch.
How to remove Enterprise Vault (EV) properties from vault enabled mailboxes . (ZAP)
10-28-2013 06:27 AM
10-28-2013 04:45 PM
Issue is currently still unresolved. I'm going to have our EV Server admin look into the ZAP article tomorrow, and I'm also slated to call in to symantec support to investigate, as we want to rebuild the profile as a last resort, as it would be quite disruptive to the user.