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

Configuring the FSA Reporting web service manually

If Enterprise Vault failed to configure the FSA Reporting web service successfully on an Enterprise Vault server, you can perform a manual configuration.

Perform these steps if you cannot access the ReportingServer web page, and the EnterpriseVaultFSAReporting application pool is not present on the Enterprise Vault server when you troubleshoot the FSA Reporting web service.

To configure the FSA Reporting web service manually

  1. Open a command prompt window on the Enterprise Vault server on which the FSA Reporting web service did not configure successfully.
  2. Navigate to the Enterprise Vault installation folder, for example C:\Program Files (x86)\Enterprise Vault.
  3. Enter the following command on a single line:

    FSAReportingWebServiceConfig create folderpath EVServer_alias

    Where the variables are as follows:

    • folderpath is the path to the FSA Reporting web service binary files. The binary files are in the FSAReporting subfolder of the Enterprise Vault installation folder, for example C:\Program Files (x86)\Enterprise Vault\FSAReporting. Enclose the path in quotes if it contains spaces.

    • EVServer_alias is the fully qualified computer alias for this Enterprise Vault server, for example server1.demo.local.

      To obtain the value of EVServer_alias, do as follows:

      • Start SQL Server Management Studio or SQL Query Analyzer and connect to the SQL Server that runs the Enterprise Vault Directory database.

      • Examine the ComputerEntry table in the EnterpriseVaultDirectory database. Use the value of ComputerName that corresponds to this Enterprise Vault server.

    If the configuration of the web service is successful, the utility returns "successful".

  4. Open Internet Explorer and enter the following URL to check whether you can now access the ReportingServer web page:

    http://EVServer_alias/FSAReporting/FSAReporting.asmx

    where EVServer_alias is the fully qualified computer alias for the Enterprise Vault server that you used in step 3.

    If you are prompted for a user name and password, add the required entries to Internet Explorer's Local intranet zone.

    See Adding the FSA Reporting web service locations to the Local intranet zone.

  5. If Internet Explorer displays an error that begins as follows when you attempt to access the ReportingServer web page, the trust level is insufficient:
    [PolicyException: Required permissions cannot be acquired.]
    System.Security.SecurityManager.ResolvePolicy(Evidence 
    evidence, PermissionSet
    reqdPset, PermissionSet optPset, PermissionSet denyPset, 
    PermissionSet& denied,
    Boolean checkExecutionPermission) +2737909
    System.Security.SecurityManager.ResolvePolicy(Evidence 
    evidence, PermissionSet
    reqdPset, PermissionSet optPset, PermissionSet denyPset, 
    PermissionSet& denied,
    Int32& securitySpecialFlags, Boolean checkExecutionPermission) 
    +57
    

    If you see this error, do as follows:

    • Navigate to the FSAReporting folder in the Enterprise Vault installation folder.

    • Open the file Web.config with a text editor such as Notepad.

    • Find the <system.web> node and add the following tag within it:

      <trust level="Full"/>

    • Save the Web.config file and try accessing the ReportingServer web page again.

  6. To ensure that the FSA reporting web service is running check the performance counters.
    • Open Windows Perfmon on each Enterprise Vault server and add the performance counter Enterprise Vault Websites\EVMOD_FSAREPORTING.

    • Confirm that the value of the connectivity counter is 1.