Chat now with support
Chat with Support

Enterprise Reporter 3.5.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

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 you must manually change a credential on a node, ensure that there are no discoveries running or queued before making the change. Change the credentials using the Services console on the host computer, then restart the service. Verify that the node started in the bottom pane of the Manage Discovery Clusters page. Restart any discoveries you canceled.
•
If a node fails to start after changing the credentials, ensure the credentials have local administrator access on the node host computer, and check that the credentials you provided are valid.
•
If a discovery fails after changing a credential, ensure that the new credentials have read access on the targets of any discovery. Check the discovery to see if it using the default node credentials or if credentials are specified. Ensure that the credentials you provided are valid.

Resolving Issues in the Configuration Manager

The Configuration Manager is used to configure your data collection. Collecting data involves your network security, which can occasionally cause problems.

•
Problems deleting a node
•
Data Collection Issues

Node Issues

•
Node Deployment Issues
•
Dealing with unassociated nodes
•
Problems deleting a node
•
Creating a Node Debug Log File

Node Deployment Issues

If something goes wrong with your node deployment, you can manually install and configure the node. When you manually install a node, it appears in the Configuration Manager as an unassociated node. You must have administrative permissions on the node host computer to install the node.

 
* 
NOTE: The node service account must be a member of the Reporter_Discovery_Nodes group for node deployment.
To manually install a node
1
If applicable, remove the node in the Configuration Manager.

 

If necessary, use the Control Panel to uninstall the node.

2
Locate the node installer, Enterprise_ReporterNode_3.5.1.xxxxx_x64.msi (where xxxxx is a unique 5-digit code), in the Quest\Enterprise Reporter\Server folder in the install location.
* 
NOTE: If you are installing the node on a remote computer, copy the appropriate Enterprise_ReporterNode_3.5.1.xxxxx_x64.msi file to that computer.
3
Run the node installer.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating