No error message displayed in the UI. However, a DTrace of the W3WP process on the CA/VAS server may list entries similar to:
[1234] (w3wp) <567> EV-L {EVSearch} {CX} EV search API Exception while getting Tags for for archiveId 123ABC456DEF789GHI123ABC456DEF789GHI0000EVSiteAlias, savesetId 190001011234567~190001010000000000~Z~1234ABCD12AB34CD56EF123456ABCDEF - System.ServiceModel.FaultException`1[KVS.Accelerator.EVSearchAPI.DataContracts.TooSlowFault]: Search targets a very large number of indexes and/or documents. (Fault Detail is equal to KVS.Accelerator.EVSearchAPI.DataContracts.TooSlowFault).
[1234] (w3wp) <567> EV-L {EVSearch} {CX} No Tag information has been returned for VaultId - 123ABC456DEF789GHI123ABC456DEF789GHI0000EVSiteAlias, savesetId - 190001011234567~190001010000000000~Z~1234ABCD12AB34CD56EF123456ABCDEF.
[1234] (w3wp) <567> EV-L {TraceTimer} {CX} [ Xms] Get Tags Details for EV archiveid 123ABC456DEF789GHI123ABC456DEF789GHI0000EVSiteAlias, savesetId 190001011234567~190001010000000000~Z~1234ABCD12AB34CD56EF123456ABCDEF, serverName
.
Each behaviour and/or symptom has a specific cause. The match information is provided to VAS via an EV Search API call, which is then processed by VAS highlighting.
The majority of behaviours and/or symptoms were traced to nuances within the HTML code of the items that prevented the VAS highlighting from highlighting the relevant terms.
For the W3WP exception above, it was determined a safety check in the code was preventing the EV Search API call from returning the match information for very large Archives.
The issue was first discovered in DA version 14.5.2, and may be present in other versions up to any fix version(s) listed below.
There are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time. However, the issue has been addressed in the revision of the product specified at the end of this article.
Please contact your Veritas Sales representative or the Veritas Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.
This issue is fixed in the following release(s), available in the Download Center at https://www.veritas.com/support:
- Enterprise Vault 15.1.3
- Enterprise Vault 15.2