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
Unable to access Report Manager on a 64-bit Windows system due to a permissions issue
Affected configurations: Report Manager running on a 64-bit Windows system.
Problem: After the deployment of Enterprise Vault Reporting's reports, Report Manager fails to open. SQL Server Reporting Services displays an Error page which states that the permissions granted to your user account are insufficient for performing this operation.
Cause: A possible cause is that the EvAzStore.xml file is not up-to-date.
Resolution: Follow this procedure to check the timestamp of the EvAzStore.xml file and if necessary, register azroles.dll manually:
- On the computer on which SQL Server Reporting Services is installed, browse to the
ReportServer\binfolder underProgram Files\Microsoft SQL Server. - Find the file
EvAzStore.xmland examine its Date Modified timestamp.If the timestamp indicates a date and time that is before the time that you first attempted to access Report Manager's home page after deploying the Enterprise Vault reports, continue with this procedure to register the Microsoft DLL file
azroles.dllmanually. - Open the Windows Control Panel, select Administrative Tools and then select Microsoft .NET Framework 2.0 Configuration.
- In the left pane of the .NET Framework 2.0 Configuration utility, expand My Computer, right-click Assembly Cache and choose Add.
- Browse to the following folder:
WINDOWS\Microsoft.NET\AuthMan\1.2 - Select the file
microsoft.interop.security.azroles.dlland click Open to add this assembly. - Close the .NET Framework 2.0 Configuration utility.
- Open the Services snap-in to the Microsoft Management Console, and restart the IIS Admin Service and the SQL Server Reporting Services.