Please enter search query.
Search <book_title>...
Enterprise Vault™ Discovery Accelerator Administrator's Guide
Last Published:
2024-09-02
Product(s):
Enterprise Vault (15.1)
- Introducing Discovery Accelerator
- Overview and latest updates
- Configuring Compliance Accelerator Desktop Client
- Importing configuration data from an XML file
- Setting Discovery Accelerator system configuration options
- 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
- Creating and viewing reports
- Enhanced reporting
- Available Discovery Accelerator reports
- Accessing reports through the OData web service
- Appendix A. Enterprise Vault properties for use in Discovery Accelerator searches
- Appendix B. Troubleshooting
- Issues with Custodian Manager
Synchronization errors after you rename the SQL Server computer
If you rename the SQL Server computer, the following message may appear in the event log of the Discovery Accelerator server when the Discovery Accelerator database synchronizes with SQL Server:
Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server. The job was not saved.
For more information on this problem and guidelines on how to resolve it, see the following article in the Microsoft Knowledge Base:
http://support.microsoft.com/?kbid=281642
You may also be able to fix the problem by running a script on the SQL Server computer.
To fix synchronization errors by running a SQL script
- Connect to your SQL Server with Query Analyzer.
- Type the following command to access the msdb database:
USE msdb
- Run the following script:
DECLARE @srv sysname SET @srv = CAST(SERVERPROPERTY('server_name') AS sysname) UPDATE sysjobs SET originating_server = @srv
Where you must replace server_name with the new name of your SQL Server computer.