Please enter search query.
Search <book_title>...
Enterprise Vault™ Compliance Accelerator Administrator's Guide
Last Published:
2023-09-05
Product(s):
Enterprise Vault (14.5)
- Introducing Compliance Accelerator
- Product documentation
- Introducing the Compliance Accelerator client
- Setting up employees and employee groups
- Working with departments
- Implementing Chinese Walls security
- Managing exception employees
- Grouping departments into partitions
- Using attributes to classify departments
- Searching for items
- About searching with Compliance Accelerator
- Building Compliance Accelerator search schedules
- Using hotwords to search for items
- Manually reviewing items
- About reviewing with Compliance Accelerator
- Escalating items
- Working with research folders
- Exporting items
- Creating and viewing reports
- Available Compliance Accelerator reports
- About viewing Compliance Accelerator datasets using the OData web service
- Appendix A. Customizing Compliance Accelerator
- Setting Compliance Accelerator system configuration options
- Appendix B. Importing configuration data from an XML file
- Appendix C. Troubleshooting
- Issues with Compliance Accelerator reports
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 Compliance Accelerator server when the Compliance 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.