Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
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
FSA Reporting scans fail to start, no change in scan status
: FSA Reporting scans fail to start for a file server. The Administration Console shows no change in scan status, and displays no error message.
A DTrace of the FSAReportingService includes the following entry:
FSAReportingUtil::GetFullyQualifiedDomainName, server name passed to this function = (NetBIOS name instead of FQDN) |
Cause: Enterprise Vault requires that both a forward DNS lookup and a reverse DNS lookup of the file server is successful.
Resolution: Make sure that both a forward DNS lookup and a reverse DNS lookup succeed for the file server.