Enterprise Vault™ Troubleshooting FSA Reporting
- About this document
- Troubleshooting an upgrade of FSA Reporting
- Troubleshooting the configuration of FSA Reporting
- Troubleshooting issues with FSA Reporting reports
- Using DTrace to troubleshoot FSA Reporting
Troubleshooting the FSA Reporting web service
To check whether the FSA Reporting web service is correctly configured and accessible on each Enterprise Vault server, proceed as follows.
To troubleshoot the FSA Reporting web service
- Start SQL Server Management Studio or SQL Query Analyzer and connect to the SQL Server that runs the Enterprise Vault Directory database.
- Enter and run the following query:
USE EnterpriseVaultDirectory SELECT WSLocation FROM FSAReportingWSLocations
- Note down all the WSLocation entries that the query returns.
Perform the remaining steps for each Enterprise Vault server mentioned in the WSLocation entries.
- 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.
- If you do not see the connectivity counter instance or if the value is 0, do as follows on each Enterprise Vault server that is specified by the WSLocation values that you found in step 3:
Open Internet Information Services (IIS) Manager.
Check under Application Pools whether the EnterpriseVaultFSAReporting application pool is present. (The following figures show IIS 6.0. The appearance is slightly different for IIS 7.0 or later.)
If the EnterpriseVaultFSAReporting application pool is not present, configure the FSA Reporting web service manually on the Enterprise Vault server.
If the application pool is present, check under Web Sites that the FSAReporting website is present.
If IIS Manager does not show the FSAReporting website, check for the presence of the log file
FSAReportingWebServiceConfigUtility.login the Enterprise Vault installation folder on the Enterprise Vault server.
If the log file is present, check its contents for further troubleshooting information.
If necessary use DTrace to perform further investigations.