Enterprise Vault™ Troubleshooting Reporting
- About this document
- Setting up SQL Server Reporting Services
- Troubleshooting configuration and report deployment
- Identifying the problem
- "Reporting has been configured on this machine. However, there were a few warnings and/or errors..." message
- Troubleshooting accessing the reports
- Troubleshooting using and exporting the reports
- Troubleshooting problems with report content
- Troubleshooting report export
Unable to view the reports
If you experience general problems with logging in or getting reports to display successfully, follow this checklist:
If you can access the Report Server web page, but you cannot see the Veritas Enterprise Vault folder, this may be due to the user account not belonging to the correct SSRS role.
See Report Server web page does not show the Enterprise Vault folder.
Make sure that you access the SQL Server Reporting Services Report Manager web application with an account that is assigned to a suitable Enterprise Vault administrator role:
See "About accessing Enterprise Vault Reporting's reports" in the Reporting guide.
Confirm that the prerequisites for Enterprise Vault Reporting are satisfied. See the following:
The section "Prerequisites for Enterprise Vault Reporting" in the Reporting guide.
The Enterprise Vault Compatibility Charts.
Make sure that you have a working network connection to the computer or computers hosting the Enterprise Vault databases.
Verify that IIS is not locked down, and that IIS services are not stopped. Try stopping and restarting IIS.
Ensure that a SQL Server login for the Reporting user account you created in the preinstallation steps is present on all the SQL servers used for the Enterprise Vault Directory database, all vault store databases, and the Monitoring database.
Ensure that the EVReportingRole role has been assigned to the Reporting user SQL Server login on all Enterprise Vault databases.
Ensure that the EVReportingRole role has been granted "SELECT" access permission for the specified views for each database.
See "Failed to deploy reports on the report server" error message.
Check whether the Reporting user account password has expired. Ideally this password should have been set never to expire, as described in the Reporting guide. If the account password has expired, you must change the Reporting user account credentials.