Enterprise Vault™ Troubleshooting FSA Reporting
- 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
File server disk space issues
Problem: FSA Reporting creates temporary data files on a file server when it scans the file server. If these files become very large, the drive that contains the files is at risk of becoming full.
FSA Reporting monitors the free space on the appropriate drive. If the free space becomes less than 100 MB by default, the FSAReportingService process shuts down and generates the following message in the event log:
The FSAReportingService process will be shut down because there is insufficient disk space on drive <drive>. Delete any unwanted files from the drive and then restart the process as follows. On file servers on which the FSA Agent is installed, restart the Enterprise Vault File Collector service. Otherwise, restart the Enterprise Vault Admin Service on the Enterprise Vault server.
Resolution: Do as follows:
If you receive this event log message, delete any unwanted files from the file server drive and then do one of the following:
For a Windows file server, restart the Enterprise Vault File Collector Service on the file server.
For a non-Windows file server that has an Enterprise Vault server as the FSA Reporting proxy server, restart the Admin Service on the Enterprise Vault server.
For a non-Windows file server that has an FSA Reporting proxy server that is not an Enterprise Vault server, restart the Enterprise Vault File Collector Service on the proxy server.
If there is likely to be insufficient space for FSA Reporting's temporary files on the file server's installation drive, we recommend that you relocate the storage location to a drive that has sufficient free space.
See "Setting the storage location for FSA Reporting's temporary files" in the Reporting guide.