Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Enterprise Reporter 3.5.1 - Report Manager User Guide

Quest Enterprise Reporter Report Manager Introducing the Report Manager Running and Scheduling Reports Creating and Editing Reports Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets

Restoring a connection to the Enterprise Reporter database

If your server has lost its connection to the database, you can still open a console and connect to the server, but functionality will be limited. You will be unable to create discoveries, run reports or modify your configuration. Ensure that the SQL Server hosting the Enterprise Reporter database is running, and that the server can access it.

The Report Manager maintains a direct connection to the SQL Server database, so ensure that the console’s computer can also access the SQL Server.

Troubleshooting Connection Timeouts

As Enterprise Reporter processes your requests, constant communication with the database is required. Depending on your network configuration, your Enterprise Reporter deployment, and the power of your SQL Server host, the solution for timeout issues may vary.

You can fix timeout issues by either increasing the timeout in Enterprise Reporter, or by investigating any systemic or deployment issues. For example, perhaps your SQL Server where the database is hosted is underpowered, or you have located your Enterprise Reporter server physically distant from your SQL Server.

There are the following settings for each timeout configuration:

Connection timeout
This is the amount of time given to make the initial connection to the database each time communication is needed. This is less likely to need adjustment. Timeouts are more likely due to SQL Server
® or network issues than Enterprise Reporter specific problems. However, if you continually are seeing timeout errors, try increasing this setting.
1
Click System Configuration.
2
Under Time-Outs, click Manage database settings used by Enterprise Reporter.

Troubleshooting credential change failures

Each credential in the Credential Manager has three parts—an account name, a password, and an optional description—you can change any of them. While most changes are processed smoothly, occasionally issues in the network environment may prevent changes from being applied. When a change fails, you must determine the reason, and manually make the changes.

If a report schedule fails after changing a credential, it could mean that:

Auditing Report Manager Activity

User activity from the Reporter Manager console is stored in the Quest Enterprise Reporter Windows Event Log on the machine for the Enterprise Reporter Server. Using this information, you can audit the following user activity for compliance purposes:

 

Create Report

2015

User <USERNAME> on machine <MACHINENAME> created report '<REPORTNAME>' (<REPORTID>)

Run Report (manual)

2016

User <USERNAME> on machine <MACHINENAME> created report '<REPORTNAME>' (<REPORTID>)

Modify Report

2017

User <USERNAME> on machine <MACHINENAME> modified report '<REPORTNAME>' (<REPORTID>)

Delete Report

2018

User <USERNAME> on machine <MACHINENAME> deleted report '<REPORTNAME>' (<REPORTID>)

You can interrogate the event log directly for object user activity information. As shown in Table 40, each event is logged with the fully qualified user name of the Enterprise Reporter user who performed the event and the machine name where the event occurred.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation