Exchange 2010, Outlook 2010, Enterprise Vault - Windows Index Issues
Hey Team,
I am having a problem with about 10% of our users where outlook returns no search results, when using the instant search feature. This issue comes and goes and will go away completely if for instance you rese the search indexer. However the issue always seems to come back. Disabling eVault doesnt seem to affect the problem, however this issue will disappear for weeks at a time so you never really know if its resolved.
The user is running Office 2010 SP1 (July 11th 2013) Update.
Enterprise Vault 10.0.3 1169 - Light Functionality, Outlook Add-in
I have reset the users search index using the microsoft tool, rebuilt his user profile - which fixed the problem for about 3 weeks. Now when the user searches for a term like "Market" or "Ticket" - It returns no results,
I looked thorugh the release notes for CU1 and CU2 for eVault and didnt see anything specific to my iussue here....
Any ideas?
Thanks,
Robert
well the thing is, you can find plenty of articles related to Outlook and searching a mailbox and it not returning results, doesn't necessarily mean that EV is involved.
In this particular circumstance in the technote, you have physical crashes of the search provider for which EV was causing to crash due to a change in how Outlook interfaced with certain DLL's
That being said I guess you'd have to look at the event logs and see if you can find any indexing logs that might give a reason as to why the result sets are blank. You could also try unisntalling EV completely from the clients and see how long the indexes stick around.
But unless you have something correlating to EV, my suggestion would be to contact Microsoft, see if they can generate any logs, see why the searches are returning blank and go from there, and if they point out that it is one of the EV components, then either have them create a TSANet case with Symantec so Microsoft and Symantec can work on it in conjunction, or take Microsofts findings and open a new case with symantec.
But as far as i'm aware, there aren't any current issues with EV causing the indexes to malfunction like that