Chatee ahora con Soporte
Chat con el soporte

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 connectivity issues

Each console maintains connections to the Enterprise Reporter server and to the SQL Server database that stores Enterprise Reporter data. A loss of either connection causes problems. Figure 12 outlines the connections between the components and the server and database.

Figure 12. Connections between components and the server and database.
Topics:  
•
Restoring a connection to the Enterprise Reporter Server
•
Restoring a connection to the Enterprise Reporter database

Restoring a connection to the Enterprise Reporter Server

There are a number of reasons why a Enterprise Reporter server may be down. When a console loses its connection to the server, it becomes unusable and must be restarted. All users connected to the Enterprise Reporter server are affected. You should check the following connections:

•
Ensure that the computer hosting the server is turned on and running properly.
•
Ensure that the Enterprise Reporter server service is running. If necessary, restart it using the Services console.
•
Ensure that you can reach the host computer over your network.
•
Ensure that the server host computer meets the minimum system requirements.

If the server has gone down and been restored since you last logged in, then the next time you connect, you will be informed that the server went down. If you are the main Enterprise Reporter administrator, this allows you to be aware that your server has had issues. Intermittent failures over time may be due to instability in your network, problems on the server’s host computer, or your SQL Server deployment.

Restoring a connection to the Enterprise Reporter database

If your server has lost its connection to the database, you can still open a console and connect to the server, but functionality will be limited. You will be unable to create discoveries, run reports or modify your configuration. Ensure that the SQL Server hosting the Enterprise Reporter database is running, and that the server can access it.

The Report Manager maintains a direct connection to the SQL Server database, so ensure that the console’s computer can also access the SQL Server.

Troubleshooting Connection Timeouts

As Enterprise Reporter processes your requests, constant communication with the database is required. Depending on your network configuration, your Enterprise Reporter deployment, and the power of your SQL Server host, the solution for timeout issues may vary.

You can fix timeout issues by either increasing the timeout in Enterprise Reporter, or by investigating any systemic or deployment issues. For example, perhaps the SQL Server om which the database is hosted is underpowered, or you have located your Enterprise Reporter server physically distant from your SQL Server.

There are two places in the Configuration Manager where you can control the database timeouts:

•
Server timeout
You can increase the timeout between the server and the database. If a timeout occurs, you will see a warning dialog box, indicating that this has occurred.
•
Cluster timeout
You can increase the timeout between the nodes in the cluster and the database. This is useful when a collection fails due to a timeout, which is indicated by an error on the Errors tab for the discovery. There are two settings for each timeout configuration:
•
Connection timeout
This is the amount of time given to make the initial connection to the database each time communication is needed. This is less likely to need adjustment. Timeouts are more likely due to SQL Server or network issues than Enterprise Reporter specific problems. However, if you continually are seeing timeout errors, try increasing this setting.
•
Command timeout
This is the amount of time allowed for the database to process requests. If you are getting timeout error messages during data collection, increase this setting.
•
Report command timeout
This is the amount of time allowed for report generation. If you are getting timeout errors messages during report generation, for interactive or scheduled reports, increase this setting.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación