Chat now with support
Chat with Support

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

Exporting Logs from the Configuration Manager

Discovery logs can be used to troubleshoot issues with discoveries. Discovery logs are collected from the Reporter server and all of the nodes within a selected cluster, and zipped into files that can be sent to Quest Support to help resolve certain collection problems. The discovery log files are all sent to the Exported Logs folder on the Reporter server. You may have several different .zip files, which may take some time to appear, depending on your configuration:

2
Click the Manage Logs button and select Export Logs.
4
Click Export.
6
Click Close.

 

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

1
Click System | Information.
2
Under Client Logging Information, click Export Configuration Manager logs.
3
Click Export.
5
Click Close.

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

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

Viewing Information About Your Enterprise Reporter Configuration

Understanding your system setup can be useful when troubleshooting. You can use the System Information page to determine where your console, Reporter server and Reporter database are hosted, what port the server is using to communicate, your software version, and other similar information you may find helpful in resolving issues.

On the Navigation pane, click System | Information.

Viewing Errors and Statistics for Tasks

For each task of a discovery, you can view collection options, errors, and statistics. These may be helpful when you experience failed collections, data that does not match your expectations, or when working on performance issues. To display the collection options for a task, hold the mouse over any column of data for that task.


Technical Documentation. 

For more information, see Viewing Errors and Error Suppressions and Viewing Statistics.

Moving the Enterprise Reporter Database

The following summary outlines line how to move the Enterprise Reporter Database from one SQL Server® to another SQL Server®.

The following procedures assume that you have the following permissions:

SQL permissions to access SQL Server® Management Studio on both the current and new SQL Server® to backup and restore the SQL database
3
Start SQL Management Studio and connect to the SQL Server® where the dbReporter database resides.
4
Under Source, select Device, click the ellipsis (…).
5
Click Add and browse to the backup copies.
6
Click Add, select the .BAK file, and click OK twice.
7
Under Backup sets to restore, select Restore beside the backup name.
8
From the Restore database window, click OK to restore the database.
3
On the Enterprise Reporter server, select All Programs | Database Wizard.
4
Choose Select/Upgrade Database and click Next.
5
Browse to (or type in the name of) the new SQL Server® and make sure the Enterprise Reporter database name is correct (for example, dbReporter), and click Next.
7
Click OK on the Database Maintenance Wizard popup that appears regarding replication.
8
Click Finish to initiate the database configuration.
9
Click OK upon completion.
1
Open Configuration Manager System | Information and confirm the database location.

 

Related Documents