Please enter search query.
Search <book_title>...
Enterprise Vault™ Discovery Accelerator Administrator's Guide
Last Published:
2019-02-05
Product(s):
Enterprise Vault (12.4)
- Introducing Discovery Accelerator
- Introducing the Discovery Accelerator client
- Setting up and assigning roles
- Working with cases
- Setting up review marks and tags
- Using rules to mark and tag items automatically
- Using Custodian Manager
- Searching for items
- About searching with Discovery Accelerator
- Defining email targets with Address Manager
- Building Discovery Accelerator search schedules
- Manually reviewing items
- About reviewing with Discovery Accelerator
- Searching within the review set
- Deleting items from Enterprise Vault archives
- Working with research folders
- Exporting and producing items
- About exporting and producing items
- Performing an export or production run
- Creating and viewing reports
- Appendix A. Customizing Discovery Accelerator
- Setting Discovery Accelerator system configuration options
- Setting Discovery Accelerator system configuration options
- Appendix B. Importing configuration data from an XML file
- Appendix C. Enterprise Vault properties for use in Discovery Accelerator searches
- Appendix D. Troubleshooting
- Issues with Custodian Manager
- Issues with Discovery Accelerator reports
Performance counter errors when the Accelerator Manager service starts
When the Enterprise Vault Accelerator Manager service starts, the following error messages may appear in the event log of the Discovery Accelerator server:
Event Type: Error Event Source: Accelerator Manager Event Category: None Event ID: 41978 Description: APP ATM - Error: deleting Performance Counters Description: Input string was not in a correct format. Event Type:Error Event Source:Accelerator Manager Event Category: None Event ID: 41980 Description: APP ATM - Error: Creating Performance Counters Description: Input string was not in a correct format.
For more information on this problem and guidelines on how to resolve it, see the following article in the Microsoft Knowledge Base: