Enterprise Vault™ Troubleshooting FSA Reporting

Resolving issues with access to FSA Reporting reports

1. Confirm that all the prerequisites for Enterprise Vault Reporting are satisfied, as described in the Installing and Configuring manual. You must have successfully configured Enterprise Vault Reporting before you can access FSA Reporting's reports.
2. Confirm that you are using versions of FSA Agent and Enterprise Vault Reporting that are compatible with FSA Reporting. See the following technical note on the Veritas Support website:

   https://www.veritas.com/docs/100030221.

3. Note that with Enterprise Vault 9.0, you cannot colocate an Enterprise Vault server and Microsoft SQL Server Reporting Services on a computer that is running Windows Server 2003 x64 edition.

   For details of supported configurations, see the Enterprise Vault Compatibility Charts.

4. Make sure that the FSA Agent is installed on target Windows file servers, and on the FSA Reporting proxy servers that are not Enterprise Vault servers.

   Do not install the FSA Agent on an Enterprise Vault server.

   If you are installing the FSA Agent on a file server that runs Windows 2000, note that the minimum requirement is Windows 2000 SP4 plus Update rollup package 1 for SP4.

5. Confirm that the FSA Agent was installed successfully by examining the following registry key:

   On a 32-bit installation of Windows:

   HKEY_LOCAL_MACHINE
    \SOFTWARE
     \KVS
      \Enterprise Vault
       \FSA
        \Reporting

   On a 64-bit installation of Windows:

   HKEY_LOCAL_MACHINE
    \SOFTWARE
     \Wow6432Node
      \KVS
       \Enterprise Vault
        \FSA
         \Reporting

   Examine this registry key in the appropriate location:

   • For a Windows file server, examine the key on the file server.

   • For a non-Windows file server examine the key on the FSA Reporting proxy server.

   Check that the WebServiceTimeout registry value is present in the key. If the value is missing, add it to the Reporting registry key. WebServiceTimeout is a DWORD value that defines the FSA Reporting web service timeout in minutes. The default value is 9999.

6. In the Administration Console, open the Targets node, select File Servers, and in the right pane view the status of FSA Reporting for each configured file server, as shown in the Reporting column. Check that Reporting is shown as On and that at least one successful scan has been performed. If Reporting is shown as Off, see the next step.

   To view the status of FSA Reporting for individual volume targets on a file server, select the target file server in the left pane of the Administration Console and view the Reporting column in the right pane. You can enable or disable FSA Reporting for a specific volume from the volume's properties, provided that Reporting is On for the file server.

   Note:

   The information provided in the FSA reports is based on data that FSA Reporting gathered from its last successful scan. If FSA Reporting has not performed a successful scan on a file server or volume, the reports will not show any information for it.

7. If Reporting for a file server is shown as Off, do as follows:

   • Right-click the node for that file server under the Targets > File Server node, and select Properties.

   • Then select the Reporting Data Collection tab and make sure that the Enable Data Collection for FSA Reporting check box is selected.

   • If necessary, perform the steps to configure a database for FSA Reporting and, for a non-Windows file server, a proxy server.

     Then click OK to apply the changes and close the dialog.

   Check whether Reporting is now shown as On for the file server in the right pane of the Administration Console. You may need to refresh the entry in the right pane by right-clicking the row showing the status for the file server and selecting Refresh. If the status is still shown as Off, try closing and reopening the Administration Console to force a refresh of the status information.

   If the status of Reporting remains Off despite data collection for the file server being enabled, there may be a problem with the FSA Reporting web service.

   See Troubleshooting the FSA Reporting web service.

8. If you are still unable to identify the problem, you can use DTrace to troubleshoot the FSAReporting component.

   See Troubleshooting FSA Reporting with DTrace.