Enterprise Vault™ Troubleshooting FSA Reporting

Last Published:
Product(s): Enterprise Vault (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

Recreating the File Collector service if it is missing

Note that this problem and solution apply only to the following Enterprise Vault releases:

  • Enterprise Vault 9.0.3, and later versions of Enterprise Vault 9.0.

  • Enterprise Vault 10.0.1, and later versions of Enterprise Vault 10.0.

Problem: On a server on which the FSA Agent is installed, the Enterprise Vault File Collector service is missing from the list of services displayed by the Windows Services snap-in. The Enterprise Vault File Placeholder service and the Enterprise Vault File Blocking service are both present, as expected.

Cause: The Enterprise Vault File Collector service has been deleted from the server in error.

Resolution: You can run the fsareportingservice command to recreate the File Collector service. When you use the command as described, it removes any remaining components of the existing File Collector service. It then installs the File Collector service and configures the service to run under the specified account. You must specify the credentials of the Vault Service account.

To recreate the File Collector service if it is missing

  1. Open a command prompt window on the server on which the service is missing.
  2. Navigate to the Enterprise Vault installation folder, for example C:\Program Files (x86)\Enterprise Vault.
  3. Run the following command:

    fsareportingservice /user domaim_name\user_name /pwd password /service

    Where:

    • domain_name is the domain name for the Vault Service account.

    • user_name is the user name of the Vault Service account.

    • password is the password of the Vault Service account.

    For example:

    fsareportingservice /user demo\vaultadmin /pwd 193xy$dq /service

  4. Use the Services snap-in to confirm that the Enterprise Vault File Collector service is now reinstated.