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

Changing the Reporting user account details

Enterprise Vault Reporting requires an Active Directory user account to use when accessing the Enterprise Vault databases. If you want Enterprise Vault Reporting to use a different user account, or if the existing account password expires, you can change the credentials of the account in either of the following ways:

To change the Reporting user account credentials using the Reporting Configuration utility

  1. If you require a new Windows user account, create the replacement account in the Active Directory domain. This account does not require a mailbox, and need not be a member of the Windows Administrators group. When you create the account:
    • Select the Password Never Expires option.

    • Leave the remaining check boxes clear (User Must Change Password at Logon, Use Cannot Change Password, Account is Disabled).

  2. Start the Enterprise Vault Reports Configuration utility.
  3. On the Reporting Configuration utility dialog box:
    • Select Reconfigure data access settings for Reporting.

    • Enter the Domain, User name, and Password for the new or modified Reporting user account.

    • Re-enter the SQL Reporting Services Instance.

    • Specify the name of the Directory database SQL Server.

    • Click Reconfigure to configure the new Reporting user account.

To change the Reporting user account credentials manually

  1. If you require a new Windows user account, create the replacement account in the Active Directory domain. This account does not require a mailbox, and need not be a member of the Windows Administrators group. When you create the account:
    • Select the Password Never Expires option.

    • Leave the remaining check boxes unselected (User Must Change Password at Logon, Use Cannot Change Password, Account is Disabled).

  2. Go to the Report Manager web application, for example http://<host_name>/reports.
  3. Log in with an account that has a content manager role on the Report Server.
  4. Click the Veritas Enterprise Vault link.
  5. Click Show Details.
  6. Click the EnterpriseVaultDS link.
  7. In Connect using, select Credentials stored securely in the report server. Then set the new user name and password and click Apply.
  8. Close the Report Manager web application.
  9. Assign the EVReportingRole role to the new Reporting user on all Enterprise Vault databases, including the Monitoring database, EnterpriseVaultMonitoring, and the Auditing database, EnterpriseVaultAudit, if it has been configured.
  10. Grant the log on locally right to the new Reporting user on the Reporting Services Report Server computer.
  11. Ensure that the new Reporting user has full control access rights on the folder <Reporting_Services_install_folder>/ReportServer/bin.