cancel
Showing results for 
Search instead for 
Did you mean: 

Reporting Server Errors EV11 SQL 2008R2

Hello there,

 

I just did a fresh installation of Enterprise Vault 11.01 with Hotfix 2 on W2012R2, everything seems to be fine, also the operation manager is running without flaws. SQL is 2008R2 on W2008R2.

 

I have some trouble with the EV reporting services (installed on SQL-Server), under Operation Reports I have several issues:

 

1) "there is no data available to display" at least at: archied Item Access, Single Instance Storage Reduction Summary, Vault Store Savesets, Vault Store Usage Summary, Content Providers Licensing and Usage Summary Report, Item Archival Rate

   

 

2) rsErrorExecutingCommand

 

- Server Seven Day Health Status

An error has occurred during report processing (rsProcessingAborted).

Query execution failed for TaskHistory-Dataset. (rsErrorExecutingCommand)

 

- Vault Store Usage Billing Account

An error has occurred during report processing (rsProcessingAborted).

Query execution failed for VaultStoreDetailsByBillingAccount-Dataset. (rsErrorExecutingCommand)

 

- Exchange Journal Mailbox Archiving Health (journal Task is running)

An error has occurred during report processing (rsProcessingAborted).

Query execution failed for Legends-Dataset. (rsErrorExecutingCommand)

 

The VSA is local administrator on the SQL-Server and content manager in reporting server (beyond other rights).

 

What can I do for Troubleshooting?

 

10 Replies

Check the schema. See:

Check the schema. See: https://www-secure.symantec.com/connect/forums/vault-store-usage-summary-no-data-available-display

Check permissions. May need to re-run Enterprise Vault Reports Configuration utility.

clip_image002.jpg

If you dtrace it it should show you the exception.

 

...I have this on some, not

...I have this on some, not all DBs:

- for instance on Store-DB

Clipboard01.jpg

does your reporting user have

does your reporting user have access in EV and EV SQL?

I just used a normal AD-user,

I just used a normal AD-user, as described in the manual. I just switched to the VSA-account - nothing changed, same error.

 

I have to make one correction: I use SQL 2012, not 2008R2

So it sounds like you've ran

So it sounds like you've ran through from page 33-39 of http://origin-symwisedownload.symantec.com/library/BUSINESS/DOC7414/EV%2011.0.1%20-%20Reporting.pdf

Did you install as the VSA?

certain reports (like some of

certain reports (like some of the ones you listed) require that you enable monitoring and/or auditing in EV. the reports wouldn't contain any data until it's gathered into the monitoring or auditing databases but i dont think they should error out like you posted.

have you followed all the instructions in the Reporting.pdf that comes with EV?

Before you install the Enterprise Vault Reporting component, you must perform the
following steps.

To prepare for the installation of Enterprise Vault Reporting
1 In the Active Directory domain, create a Windows user account named, say,
"ReportingUser", for Enterprise Vault Reporting to use when accessing the
Enterprise Vault databases. This reporting user account does not require a
mailbox, and it need not be a member of the Windows Administrators group.
When you create the reporting user account:
■ Select the Password Never Expires option.
■ Leave the remaining check boxes clear (User Must Change Password
At Logon, User Cannot Change Password, and Account Is Disabled).
2 Give the Vault Service account a "Content manager" role on the Microsoft SQL
Server Reporting Services server. Refer to the Microsoft documentation for
instructions on how to assign Microsoft SQL Server Reporting Services roles
to user accounts.
3 Add the Vault Service account to the Local administrators group on the Microsoft
SQL Server Reporting Services server computer.

To configure Enterprise Vault Reporting
1 Log on to the computer under the Vault Service account.
2 Start the Reporting Configuration utility, Enterprise Vault Reports
Configuration.
3 Choose the option Configure Reporting and deploy or upgrade reports.
4 Provide the details of the reporting user account you created for Enterprise
Vault Reporting to run under. Enter the Active Directory domain, the user name,
and the password for the account.
5 Select the Microsoft SQL Server Reporting Services instance on which you
want to deploy the reports. To deploy the reports on the default instance, select
the instance name MSSQLSERVER.
6 Select the language that you want the reports to use.
7 Select the Directory database SQL Server. If the server does not appear in the
list, type in the name of the server.
8 Click Configure.
9 When the utility has finished, click OK on the displayed dialog to quit the utility.
10 If this is the first time that you ran the Reporting Configuration utility, check that
the configuration was successful.
See “Checking that the configuration of Enterprise Vault Reporting was
successful” on page 37.
11 Enable the synchronization of Enterprise Vault Reporting roles-based security
on the computers on which you use Authorization Manager to manage
administrator roles.
See “Enabling the synchronization of Enterprise Vault Reporting roles-based
security” on page 37.

To check that the configuration of Enterprise Vault Reporting was successful
1 Check that the reporting user account has an SQL login on the SQL servers
that hold the following databases:
■ The Enterprise Vault Directory database
■ The Enterprise Vault Monitoring database
■ The Enterprise Vault Audit database
■ All vault store databases
■ All vault store group fingerprint databases
■ All FSA Reporting databases, if you have configured FSA Reporting
If a logon does not exist on all these SQL servers, create it.
2 Check that the SQL server role EVReportingRole has been added to each
Enterprise Vault database, and that this role has been assigned to the reporting
user

Have a look at this as well

Have a look at this as well if you have not already: https://support.symantec.com/en_US/article.TECH51288.html

I will re-check

I will re-check everything.

 

Hell, this is really a bunch of work. The focus lies on archiving and usage of EV in a serious manner, and therefore you have to deal with lots of configuration options and deep understanding of this product.

 

This leads to the final question: are the reporting services worth so far? Does anybody use the reporting services and gains benefit for a 2000-User installation over the built in reporting via EV-console and operation manager??

Yeah it can be a pain

Yeah it can be a pain sometimes. It is nice to have just to get an overview of everything. But I also like to use a lot of SQL queries to find the data I'm looking for. It's just preference, but it is easier to have it right there for you. The Usage.asp page is good though.

what can i say? "a lot of

what can i say? "a lot of work" and "worth it" are both relative terms. in my experience, the pre-requisites are pretty basic. it's all in the planning and if this is your first time, seems to me that you're doing pretty well so far.