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
'Failed to upgrade FSA Reporting database' event log error message
Problem: After an upgrade from Enterprise Vault 8.0 to any version of Enterprise Vault 9.0, the following error message appears in the Enterprise Vault event log:
Failed to upgrade FSA Reporting database EnterpriseVaultFSAReporting, SQL Server %1. Error: %2
where %1 is the name of the SQL Server and %2 provides more information about the error.
Cause: The Enterprise Vault 8.0 FSA Reporting database did not upgrade successfully to Enterprise Vault 9.0.
Resolution: To identify the exact cause of the upgrade failure, examine the log file FSAReportingWebServiceConfigUtility.log, located in the Reports subfolder of the Enterprise Vault installation folder, for example C:\Program Files (x86)\Enterprise Vault.
One possible cause is that Enterprise Vault cannot connect to the SQL Server that hosts the FSA Reporting database. Make sure that you can connect to the SQL Server computer from the Enterprise Vault server on which you run the upgrade.
In many cases the problem is that Enterprise Vault was unable to put the EnterpriseVaultFSAReporting database into single user mode. If the log file indicates that this is the cause, do as follows:
Make sure that all existing connections to the EnterpriseVaultFSAReporting database are closed.
Then restart the Enterprise Vault Directory service, to trigger another attempt to upgrade the EnterpriseVaultFSAReporting database.