Chat now with support
Chat with Support

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

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.2.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.2.xxxxx_x64.msi file to that computer.
3
Run the node installer.
* 
NOTE: If the network is using Kerberos for authentication, then there is an option to enter a UPN or SPN for the node to communicate with the Enterprise Reporter server.

Dealing with unassociated nodes

An unassociated node is one that has been either manually installed, or left behind from a previous installation of Reporter. You can either uninstall the node, or associate the node with a cluster.

To uninstall a node
•
Use the Control Panel, and uninstall Quest Enterprise Reporter Node.
To associate a node with a cluster
1
In the Manage Discovery Clusters pane, select the cluster.
2
In the Unassociated Nodes pane, select the node.
3
Click Associate Node(s) with Selected Cluster.
4
In the confirmation dialog box, click Yes.
5
If necessary, close the Unassociated Nodes pane.
The node appears associated with the cluster in the Initializing state until it is deployed.

Problems deleting a node

If you are deleting a node, you may see an error message indicating that the discovery node installation failed, for example:
"An error occurred copying the discovery node installation program Quest.Reporter.Core.Server.MsiInstaller.exe to \\servername\ADMIN$\Quest.Reporter.Core.Server.MsiInstaller.exe."

This indicates that there was a problem connecting to the host computer. Check your node credentials, ensure that the firewall is not enabled on the host, and ensure that the computer can be reached on the network. Once you have resolved the connection issue, you can attempt to remove the node again.

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.

* 
IMPORTANT: Use caution when increasing the logging level. We recommend that you do not increase the level permanently, as it may affect node performance. The logging levels are cumulative, so Debug contains debug, information, warnings, errors and fatal errors.
To create a node debug log file
1
In the Manage Discovery Clusters pane, select the cluster.
* 
NOTE: The cluster must be enabled to change the node logging level.
2
On the Cluster Details tab in the bottom pane, change the node logging level to Debug.
3
Increase the size of the node log files.
4
Click Apply.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating