Enterprise Vault™ Troubleshooting Reporting
- About this document
- Setting up SQL Server Reporting Services
- Troubleshooting configuration and report deployment
- About troubleshooting configuration and report deployment
- About using DTrace with Microsoft SQL Server Reporting Services
- Identifying the problem
- "Reporting Configuration Utility is unable to copy file..." message
- "Reporting has been configured on this machine. However, there were a few warnings and/or errors..." message
- "Authentication failed for reporting user" error message
- "The specified SQL Server does not exist" error message
- "Ensure that you can browse to the Report Manager..." error message
- "EnterpriseVaultDirectory database does not exist..." error message
- "Failed to connect to the specified SQL Server with the credentials you provided" error message
- "Failed to deploy reports on the report server" error message
- Error code 1 and log file error "System Net.Web Exception: Page cannot be found"
- Log file error "Assembly security permission grant set"
- "Couldn't disable MyReports" error
- Configuring Reporting and deploying the reports
- Troubleshooting accessing the reports
- About troubleshooting accessing the reports
- Unable to view the reports
- Report Server web page does not show the Enterprise Vault folder
- Role assignments and changes fail to get implemented
- Unable to access Enterprise Vault reports from a different domain
- Unable to access Report Manager on a 64-bit Windows system due to a permissions issue
- Changing the Reporting user account details
- Troubleshooting using and exporting the reports
- About troubleshooting using and exporting the reports
- Troubleshooting problems with report content
- Images or data fail to appear
- Reports omit data related to some vault stores
- No information appears in the Data Analysis reports
- No information appears in reports that use Monitoring data
- No information appears in reports that use auditing data
- Domino Server Journal Mailbox Archiving Health report: Unable to distinguish between Domino journal mailbox locations
- Troubleshooting report export
- About using Reporting with multiple Reporting Services
Role assignments and changes fail to get implemented
Problem: You make changes to the Enterprise Vault roles-based security from Authorization Manager in the Administration Console, but these changes do not get implemented.
Cause: This problem may be due to caching latency. If you add, remove or change roles from Authorization Manager and then save your changes, there is a latency of about one minute before you can successfully make further changes.
Resolution: After applying changes to roles in Authorization Manager, wait at least one minute for the changes to take effect, before you start Authorization Manager again to make further role assignments or changes.
See the procedures for assigning, modifying, and creating roles under Roles-based administration in the Administrator's Guide.
Note that you must also enable the synchronization of Enterprise Vault Reporting roles-based security.
See "Enabling the synchronization of Enterprise Vault Reporting roles-based security" in the Reporting guide.