Chat now with support
Chat with Support

Enterprise Reporter 3.2.2 - Installation and Deployment Guide

Product Overview Installation Considerations for Enterprise Reporter Installing and Configuring Enterprise Reporter Managing Your Enterprise Reporter Deployment Troubleshooting Issues with Enterprise Reporter Appendix: Database Content Wizard Appendix: Encryption Key Manager Appendix: Log Viewer

Problems Opening the Consoles

If you have UAC enabled, ensure that you have Administrator permission to open the console at an elevated level.

To open a console, you must be assigned one of the Enterprise Reporter roles.
For more information, see Role Based Security in Enterprise Reporter .

Technical Documentation.

If you are unable to log into the Configuration Manager, verify the type of groups you have selected during installation and how you are adding accounts to those groups to give them access to Enterprise Reporter.

For more information, see Configuring the Database and Security Groups .

Technical Documentation.

 

Database Configuration Issues

When you install the Enterprise Reporter server, you must configure your database. Occasionally, you may get errors when you perform the creation and setup of your database. The source of database configuration error message varies depending on how you attempted to create the database:

•
During the installation of the server, these errors appear on the last page of the installation wizard.
•
Using the database wizard, these errors appear as the wizard proceeds through the process of creating the database.
•
To aid with troubleshooting, errors generated during database configuration are also written to the following log file: \ProgramData\Quest\Enterprise_Reporter\DatabaseMaintenance.log

When you are troubleshooting these installation errors, generally the cause is credential related. You can create a database using either Windows® or SQL credentials:

•
Windows® credentials are those you logged in as
•
SQL credentials are optionally provided when you create the database, either during installation or using the Database Wizard.

One solution is to create a new database using credentials that have the database creation right. Once the database is created, you can use the Save Connection Information option in the Database Wizard to connect to the database using your own credentials. If you have a partially created database that you want to remove from the server, you can use the Database Wizard to do this. See Deleting a Database . You may need to have an administrator with the database creation right run the Database Wizard or installer to create the database.

The following table outlines possible solutions to each error.

 
Table 29.  
Error
potential causes
potential solutions

Could not create a Database

The credentials you used are not assigned the Database Creator role on the target SQL Server®.

Create a new database using the Database Wizard. For more information, see Using the Database Wizard to Create or Connect a Database .

Ensure that your domain controllers have replicated, and then create a new database using the Database Wizard.

Could not create all groups

The credentials you used do not have permissions to create groups on the domain .

Have an administrator with the group creation permission run the Database wizard to remove the existing database and create a new database. For more information, see Using the Database Wizard to Create or Connect a Database .

Could not create all logins

The credentials you used do not have permissions to create logins.

Groups may not exist on the domain controller to which the SQL Server® is connecting.

Verify that the groups exist on the domain.

Have a SQL administrator run the Database wizard to remove the existing database and create a new database. For more information, see Using the Database Wizard to Create or Connect a Database .

Could not create all SQL roles

The credentials you used may not have SQL role creation permissions on SQL Server®.

Have a SQL administrator run the Database wizard to remove the existing database and create a new database. For more information, see Using the Database Wizard to Create or Connect a Database .

Could not add Service account to all groups

The groups may not have been created.

The service account may not exist on the domain or SQL Server®.

The credentials you used may not have permissions to add account to groups.

Verify that the groups and Service account exist.

Have an administrator manually add the service account to the appropriate groups.

Could not start NT service

Service cannot connect to database.

Problems with account used to run the service.

Verify that the service account or SQL login used by the service has permissions to read and write to the database.

Verify that the service account is valid and has permissions to login as service.

Troubleshooting Connectivity Issues

Each console maintains connections to the Enterprise Reporter server and to the SQL Server® database that stores Enterprise Reporter data. A loss of either connection causes problems. Figure 12 outlines the connections between the components and the server and database.

Figure 12. Connections between components and the server and database.
Topics:  
•
Restoring a Connection to the Enterprise Reporter Server
•
Restoring a Connection to the Enterprise Reporter Database

Restoring a Connection to the Enterprise Reporter Server

There are a number of reasons why a Enterprise Reporter server may be down. When a console loses its connection to the server, it becomes unusable and must be restarted. All users connected to the Enterprise Reporter server are affected. You should check the following connections:

•
Ensure that the computer hosting the server is turned on and running properly.
•
Ensure that the Enterprise Reporter server service is running. If necessary, restart it using the Services console.
•
Ensure that you can reach the host computer over your network.
•
Ensure that the server host computer meets the minimum system requirements.

If the server has gone down and been restored since you last logged in, then the next time you connect, you will be informed that the server went down. If you are the main Enterprise Reporter administrator, this allows you to be aware that your server has had issues. Intermittent failures over time may be due to instability in your network, problems on the server’s host computer, or your SQL Server® deployment.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating