Enterprise Vault™ Troubleshooting Reporting

Last Published:
Product(s): Enterprise Vault (14.1, 14.0, 12.5, 12.4, 12.3, 12.2, 12.1, 12.0)
  1. About this document
    1.  
      About this technical note
    2.  
      About troubleshooting Enterprise Vault Reporting
  2. Setting up SQL Server Reporting Services
    1.  
      About Setting up SQL Server Reporting Services
  3. Troubleshooting configuration and report deployment
    1.  
      About troubleshooting configuration and report deployment
    2.  
      About using DTrace with Microsoft SQL Server Reporting Services
    3. Identifying the problem
      1.  
        "Reporting Configuration Utility is unable to copy file..." message
      2. "Reporting has been configured on this machine. However, there were a few warnings and/or errors..." message
        1.  
          About Enterprise Vault auditing
        2.  
          About FSA Reporting
      3.  
        "Authentication failed for reporting user" error message
      4.  
        "The specified SQL Server does not exist" error message
      5.  
        "Ensure that you can browse to the Report Manager..." error message
      6.  
        "EnterpriseVaultDirectory database does not exist..." error message
      7.  
        "Failed to connect to the specified SQL Server with the credentials you provided" error message
      8.  
        "Failed to deploy reports on the report server" error message
      9.  
        Error code 1 and log file error "System Net.Web Exception: Page cannot be found"
      10.  
        Log file error "Assembly security permission grant set"
      11.  
        "Couldn't disable MyReports" error
    4.  
      Configuring Reporting and deploying the reports
  4. Troubleshooting accessing the reports
    1.  
      About troubleshooting accessing the reports
    2.  
      Unable to view the reports
    3.  
      Report Server web page does not show the Enterprise Vault folder
    4.  
      Role assignments and changes fail to get implemented
    5.  
      Unable to access Enterprise Vault reports from a different domain
    6.  
      Unable to access Report Manager on a 64-bit Windows system due to a permissions issue
    7.  
      Changing the Reporting user account details
  5. Troubleshooting using and exporting the reports
    1.  
      About troubleshooting using and exporting the reports
    2. Troubleshooting problems with report content
      1.  
        Images or data fail to appear
      2.  
        Reports omit data related to some vault stores
      3.  
        No information appears in the Data Analysis reports
      4.  
        No information appears in reports that use Monitoring data
      5.  
        No information appears in reports that use auditing data
      6.  
        Domino Server Journal Mailbox Archiving Health report: Unable to distinguish between Domino journal mailbox locations
    3. Troubleshooting report export
      1.  
        CSV format: All data appears in a single cell in Excel
      2.  
        Excel format: Date and timestamp does not appear
      3.  
        XML file format: "Page cannot be displayed" error
      4. Known Issues with report export
        1.  
          DBCS characters unreadable in PDF format
        2.  
          Archive quota usage report: Problems when exported in CSV or XML format
        3.  
          CSV and XML format Data Analysis reports omit table header information
    4.  
      About using Reporting with multiple Reporting Services

"Ensure that you can browse to the Report Manager..." error message

Symptoms: The Reporting Configuration utility displays the following error message: 

Ensure that you can browse to the Report Manager Web application and 
view its Home page successfully. The URL has the format 
http://host_name/webapp_name/, for example 
http://myserver.mydomain.com/Reports/. When you have displayed the 
Report Manager Home page, click 'OK' below to continue.

Cause: This message appears if the Configuration utility is unable to access the Microsoft Reporting Services Report Manager web application.

Resolution: Make sure that the Microsoft SQL Server Reporting Services are configured and running.

Then follow the error dialog instructions to browse to the Report Manager web application's home page. When you have successfully accessed the web application home page, click OK on the error dialog to continue the configuration.

If the same error dialog reappears when you click OK, refresh the Report Manager home page and then click OK on the dialog again. On a slow Report Server you may need to repeat these actions a number of times until the error dialog no longer appears and the reports deploy successfully.