Updated Compatibility Guide - September 26th
WIth the release of 10.0.2 we've updated the compatibility guide. Key additions are: SQL2012 - Support with 10.0.2 SQL 2008 R2 SP2 - Support with EV9 -> EV10 New IPv6 Section FSA Support for Windows 2008 Core Server FSA - New Unix,Linux & NFS table Obviously there's other various updates but please make sure you're using the latest guide available at the usual place....just here. http://www.symantec.com/business/support/index?page=content&id=TECH38537Enterprise Virtual Vault Error in Outlook 2016
I recently upgraded my OS to Windows 10 from Windows 7. I also upgraded to MS Office 2016 (from MS Office 2010). Finally, I upgraded Enterprise Vault to Version 11 with the Hotfix 3 (From Version 10). Here's the issue: I can successfully sync my vault with my mailbox, but I'm having a problem adding my vaultto Outlook (and accessing my vault files). When I try to add my Virtual Vault to my Outlook Navigation Pane, I get the following error: "Enterprise Vault Could Not Add or Remove the Following Virtual Vaults" Any suggestions on how to fix this issue? Thanks! DanEV11 - indexing running behind? Check this
Hello all, I've been working on an issue we had the last few weeks, where the VAC reported 'items waiting to be indexed', and where the count went up day by day. While working with support, and in this forum, I also accidentally found an KB article of Symantec, describing hanging searches on DA/CA. As these use the indexes, I read the article. The article mentions that a specific Microsoft Update can cause issues with certain programms (TSM, SEP) and affects ASP, .Net and IIS. Hm... Indexing uses these too. We initially left archiving tasks in reportmode, to allow indexing to cactch up, ran dtraces etc. No succes. Support advised we might need to reinstall the indexing binaries. I decided to first have the updated MS Update applied. After having that update applied, and the EV-servers rebooted, indexing catched up. The VAC now shows "No problems detected". Information can be found here: The Symantec article: http://www.symantec.com/docs/TECH232439 The updated MS KB article: https://support.microsoft.com/en-us/kb/3092627 I hope this assists some of you in figuring out in resolving the issue (if you encounter this) Regards, GJ
