Chat now with support
Chat mit Support

Enterprise Reporter 3.2.2 - 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

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


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

Run Report (manual)


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

Modify Report


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

Delete Report


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 39, 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.

Exporting Logs from the Report Manager

This section gives an overview of how to export logs from the Report Manager.

See also:

The Report Manager logs can be used to troubleshoot issues with the Report Manager service. Information is collected from the Report Manager service and is zipped into log files that can be sent to Quest Support to help resolve certain Report Manager problems. The log files are sent to the desktop on the Report Manager computer and may take some time to appear, depending on your configuration:

Click System | Information.
Under Client Logging Information, click Export Report Manager logs.
Click Export.
Click Close.

You can unzip and view the Report Manager logs using the Log Viewer.

Click System | Information.
Under Log Viewer, click View logs to open the Log Viewer.

Resolving Issues in the Report Manager

The Report Manager is used to generate reports using the data collected by the Configuration Manager. There are some issues that may occur while using this console.

See also:

What To Do if the Data in Your Report is Not What You Expect

There are a number reasons why there may be no data or data that is unexpected. The following table outlines some of the possible problems and solutions.

Your report has different data than the last time you ran it, and you do not think it should.

Check your parameter values, and ensure that you are running the correct report. If you are running a scheduled report, ensure that no changes were made to the underlying report. For more information, see Scheduling Reports .

If this does not address the issue, it is possible there is a data collection issue, such as scopes or tombstoning. Inform your Enterprise Reporter administrator. For more information, see the Quest Enterprise Reporter Configuration Manager User Guide in the Technical Documentation.


You supply values for the supplied parameters, but your report has no data.

The parameters are joined together with AND logic. This means that if you supply values for parameters, all the values have to be true for all data in the report. Remove the values and rerun the report to determine if this is the issue.

Your report does not return the data you were expecting, even with no values provided for the parameters.

Examine the report definition to ensure that fields you need are included in the report, and that there are no parameters that would prevent the expected data from appearing, including hidden parameters. If you need to customize the report, see Editing Reports and Viewing Report Properties .

Your groups appear to have incomplete members.

Group membership is an option in NTFS and SQL Server® discoveries.For more information, see the Quest Enterprise Reporter Configuration Manager User Guide in the Technical Documentation.


Your report does not have any data.

If no other solution works, it is possible that no data has been collected. Collections are performed using the Configuration Manager. Contact your Enterprise Reporter administrator to ensure a proper discovery is created to cover the scope of your report.

After upgrading, editing older reports can result in missing data for a field.

Check with your Enterprise Reporter administrator to see if the field is an extended field—extended attributes have (extended) after them. It is likely that is now collected by default, and you can replace the extended attribute with the default in the report.

Data does not seem to be updated for a specific field

Check with your Enterprise Reporter administrator to see if the field is still being collected. Administrators can manage which attributes are collected.

You have used the * wildcard as a parameter value, but no data is returned.

A number of parameters included in the Library reports have been specially developed to be easier to use. You must select values from the list of options in order to see results in your report.

You are scheduling a report, and you are denied access to a share.

Ensure that the credentials have write access to the target share. If the share is located on the Reporter server, the server credentials are used. If the share is not located on the Reporter server, the credentials specified when creating the schedule are used.

You need to change the format of the data in your report. For example, your report is showing a computer using the fully qualified domain name, and you would like it to show the common name.

Use a custom query report. To make things easier, you can copy the query from an existing report into a query editor, make the necessary changes, and then paste the new query into the custom query report.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen