Enterprise Vault™ Troubleshooting FSA Reporting

Last Published:
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)
  1. About this document
    1.  
      About this technical note
    2.  
      About troubleshooting FSA Reporting
  2. Troubleshooting an upgrade of FSA Reporting
    1.  
      About troubleshooting an upgrade of FSA Reporting
    2.  
      'Failed to upgrade FSA Reporting database' event log error message
    3.  
      Archive information is not shown for some volumes
  3. Troubleshooting the configuration of FSA Reporting
    1.  
      About troubleshooting the configuration of FSA Reporting
    2.  
      Error message 'Not able to resolve file server FQDN for this file server'
    3.  
      FSA Reporting scans fail to start, no change in scan status
    4.  
      Error message 'Enterprise Vault cannot enable/disable the FSA Reporting data collection settings now'
    5.  
      Error message: 'Enterprise Vault cannot access the FSA Reporting web service'
    6.  
      Error message: 'Could not connect to FSAReporting virtual server'
    7.  
      File server disk space issues
    8.  
      Warning message 'Total number of file types exceeds one thousand'
    9.  
      Problems after failover in a building blocks environment
    10.  
      Recreating the File Collector service if it is missing
    11.  
      Troubleshooting the FSA Reporting web service
    12.  
      Adding the FSA Reporting web service locations to the Local intranet zone
    13.  
      Configuring the FSA Reporting web service manually
  4. Troubleshooting issues with FSA Reporting reports
    1.  
      About troubleshooting issues with the FSA Reporting reports
    2.  
      Troubleshooting accessing the FSA Reporting reports
    3.  
      'File Group Space Usage on a Server' report shows double the number of files on some target volume shares
  5. Using DTrace to troubleshoot FSA Reporting
    1.  
      About using DTrace to troubleshoot FSA Reporting
    2.  
      Troubleshooting FSA Reporting with DTrace

Problems after failover in a building blocks environment

Problem: After a failover of a system in a building blocks environment with FSA Reporting configured, FSA Reporting stops working. The following error appears in the Enterprise Vault event log, even though the service is running:

FSA Reporting Web service is not running

Cause: The Directory service or the FSA Reporting web service or both are not accessible on Windows file servers.

Resolution: After a failover, you must change the DNS alias of the failed Enterprise Vault server so that it maps to a working server. See step 1 of the procedure in the section "Configuring a working building blocks solution" in the Administrator's Guide.

When you have performed this step, open a command prompt window on the Enterprise Vault server and run the following commands:

ipconfig /flush
ipconfig /register

Then continue with the remaining steps in the procedure "Configuring a working building blocks solution" in the Administrator's Guide, to update the service locations.