Search <book_title>...

Enterprise Vault™ Troubleshooting Reporting

Last Published: 2021-03-23

Product(s): Enterprise Vault (14.1, 14.0, 12.5, 12.4, 12.3, 12.2, 12.1, 12.0)

"Failed to deploy reports on the report server" error message

Symptoms: The Reporting Configuration utility displays an error message similar to the following:

Failed to deploy reports on the report server. Please refer to the 
EVDeployreports.log file and to the 'Troubleshooting 
Enterprise Vault Reporting' article for more details.

Note:

If you get this message, run the Enterprise Vault reports that you intend to use. If the reports contain data, then you can ignore the message.

Remember that if you have configured FSA Reporting, the Data Analysis reports do not show data for a file server or a volume until FSA Reporting has performed a successful scan on that file server or volume.

Cause: One of the following problems may have occurred during the report deployment:

A SQLException occurred when the Reporting Configuration utility attempted to do any of the following:
- Add the Reporting user account to the Enterprise Vault databases.
- Create the role EVReportingRole on the auditing database.
- Grant 'SELECT' access permissions to the EVReportingRole.
The Reporting Configuration utility was unable to set access for the Reporting user on the Report Server's bin folder.

Resolution: If you run all the Enterprise Vault reports you intend to use and they contain data, you can ignore the message that the reports failed to deploy successfully.

If any of the reports do not contain data, work through the following steps:

A likely reason for the 'Reports failed to deploy successfully' message is the absence of an auditing database or an FSA Reporting database. These databases are required for some of Enterprise Vault Reporting's reports:
- The auditing database is required for two of the Operation reports, Archived Items Access and Archived Items Access Trends. If the auditing database is absent, you will see entries similar to the following in EVDeployReports.Log:
```
EnterpriseVaultAuditDb is not configured

Database: EnterpriseVaultAudit, SQL Server: MyServer 
Error connecting
```
  Note:
  If you do not want to use the archived items access reports, you can ignore these log entries.
  If you want to use the Archived Items Access and Archived Items Access Trends reports, you must enable Enterprise Vault auditing.
  For information on enabling Enterprise Vault auditing, see the Administrator's Guide.
- An FSA Reporting database is required for all the Data Analysis reports. If the FSA Reporting database is absent, entries similar to the following appear in EVDeployReports.Log:
```
EnterpriseVaultFSAReportingDb is not configured

Database: EnterpriseVaultFSAReporting, SQL Server: MyServer 
Error connecting
```
  Note:
  If you do not want to use the Data Analysis reports, you can ignore these log entries.
If EVDeployReports.Log indicates another problem, work through the rest of the steps below. You can ignore some of the entries in the log.
See Identifying the problem.
Ensure that a SQL Server login for the Reporting user account is present on the SQL servers used for the Enterprise Vault Directory database, all Vault store databases, and the Enterprise Vault Monitoring database.
Ensure that the EVReportingRole role has been assigned to the Reporting user SQL Server login on all Enterprise Vault databases.

Ensure that, for each database listed in the following table, the EVReportingRole role has been granted SELECT access permission for the specified views.

Database	View
EnterpriseVaultAudit	EVAuditView
EnterpriseVaultDirectory	ArchiveView
	ComputerServiceTypeView
	VaultEntryView
	view_ComputerEntry
	view_ComputerTask
	view_DominoMailboxArchivingStatus
	view_ExchangeMailboxArchivingStatus
	view_ExchangeMailbox_Server
	view_ExchangeServerEntry
	view_MonitoringSettings
	view_NotesJournal_Server_Domain
	view_NotesMailServerEntry
	view_NotesMailServer_Domain
	view_NotesMailboxArchivingStatus
	view_PartitionEntry
	view_PolicyTargetGroup_PolicyEntry
	view_ReportSettings
	view_Root
	view_Site
	view_Storage_VaultStoreEntry
	view_Trustee
EnterpriseVaultMonitoring	JrnMailBoxParametersView
	MailboxParameterConfigView
	view_DominoJrnMailBoxParameters
	view_MailboxMonitoringHistory
	view_ServiceMonitoringHistory
	view_TaskMonitoringHistory
Vault Store database(s)	view_Collection
	view_ListVaults
	view_SaveSet
	view_Saveset_Archive_Vault
	view_Saveset_Propertie
	view_VaultStoreSummary

Ensure that the Reporting user has been granted "log on locally" rights on the Reporting Services Report Server computer.
Ensure the Reporting user has full control access rights on the folder <Reporting_Services_install_folder>/ReportServer/bin.
Try to access the reports. If you continue to have problems you may have to troubleshoot.
See About troubleshooting accessing the reports.
See About troubleshooting using and exporting the reports.