Please enter search query.
Search <book_title>...
Enterprise Vault™ Compliance Accelerator Administrator's Guide
Last Published:
2024-03-04
Product(s):
Enterprise Vault (15.0)
- Introducing Compliance Accelerator
- Introducing Veritas Surveillance
- Creating and viewing reports
- About the Compliance Accelerator reports
- Accessing data through the Microsoft SQL Server Reporting Services (SSRS)
- Enhanced reporting
- Accessing reports through the OData web service
- Configuring a Power BI template for reporting
- Appendix A. Troubleshooting
- Veritas Surveillance user interface user interface is not displayed properly in non-English environment
- Issues with the random sampling of items
- Display issues when you open a Compliance Accelerator website in Internet Explorer 10 or later
- Vault stores not displayed in the Veritas Surveillance web client
- TNEF-encoded attachments to Internet Mail (.eml) messages may not be readable after you export the messages from a review set
- Synchronization errors after you rename the SQL Server computer
- Performance counter errors when the Accelerator Manager service starts
- SQL Service Broker warning when restoring a customer database to a different server
- Error messages when the Intelligent Review (IR) API authentication and authorization fails
- Known issues after enabling FIPS
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 Compliance 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: