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
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.