Please enter search query.
Search <book_title>...
Enterprise Vault™ Troubleshooting FSA Reporting
Last Published:
2021-03-23
Product(s):
Enterprise Vault (14.1, 14.0, 12.5, 12.4, 12.3, 12.2, 12.1, 12.0, 11.0.1, 11.0)
- About this document
- Troubleshooting an upgrade of FSA Reporting
- Troubleshooting the configuration of FSA Reporting
- About troubleshooting the configuration of FSA Reporting
- Error message 'Not able to resolve file server FQDN for this file server'
- FSA Reporting scans fail to start, no change in scan status
- Error message 'Enterprise Vault cannot enable/disable the FSA Reporting data collection settings now'
- Error message: 'Enterprise Vault cannot access the FSA Reporting web service'
- Error message: 'Could not connect to FSAReporting virtual server'
- File server disk space issues
- Warning message 'Total number of file types exceeds one thousand'
- Problems after failover in a building blocks environment
- Recreating the File Collector service if it is missing
- Troubleshooting the FSA Reporting web service
- Adding the FSA Reporting web service locations to the Local intranet zone
- Configuring the FSA Reporting web service manually
- Troubleshooting issues with FSA Reporting reports
- Using DTrace to troubleshoot FSA Reporting
Archive information is not shown for some volumes
Problem: After an upgrade from Enterprise Vault 8.0 to any version of Enterprise Vault 9.0, the archive information for some volumes does not appear in the reports.
Cause: You have not migrated the FSA metadata in all of your vault store databases.
Resolution: After the upgrade to Enterprise Vault 9.0 you must use the FSA upgrade utility to migrate the FSA metadata for all the vault stores that contain FSA items.
See "Upgrading the FSA metadata" in the Enterprise Vault 9.0 Upgrade Instructions, and the "FSA upgrade utility" section of the Utilities guide.