Tchater maintenant avec le support
Tchattez avec un ingénieur du 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

Creating a Node Debug Log File

If you are experiencing difficulty, the support staff may ask you to change the logging level for nodes in a cluster. The default setting for node logging is Warning, which also includes Fatal and Error. You can increase the logging level to Information or Debug to help them troubleshoot your issue. You also should increase the size of the node log files temporarily to accommodate the increased data collection.

4
Click Apply.

Data Collection Issues

You may run into situations where not all of your data is collected, or even no data at all. The first thing you need to determine is what tasks in the discovery are failing. Once you have located the problem tasks, you can use the errors and statistics generated to pinpoint the problem. There are several other things you can examine:

If your discovery fails for all tasks, it is possible that your shared data location is the problem. The shared data location may no longer exist, or the node may not have adequate access to it. Check the errors on the discovery task to investigate. For more information, see Viewing Errors and Error Suppressions . If this is the issue, ensure the shared data location belonging to the cluster exists and is properly permissioned. Shared data locations are not used for Active Directory, Exchange, or NTFS discoveries.
The node may not have access to that server. Check your credentials, and change them if necessary. For more information see Node Credential and Alternate Credential Details for On-Premises Discoveries and Modifying Node Credentials .
If you have used alternate credentials for the discovery, ensure that they are permissioned properly. For more information, see Node Credential and Alternate Credential Details for On-Premises Discoveries and Detailed Permissions for Enterprise Reporter Discoveries .

Troubleshooting Features in Enterprise Reporter

There are several features in Enterprise Reporter to help you solve problems.

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.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation