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.
There are the following 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. |
There are two types of database timeout settings in the Configuration Manager:
1 |
Click Configuration. |
2 |
Click Manage database settings. |
1 |
Click Manage Discovery Clusters. |
3 |
Click the Cluster Details tab. |
Once you have changed credentials, review the following:
• |
The following information is provided in the event log.
You can interrogate the event log directly for object user activity information. As shown in Table 44, each event is logged with the fully qualified user name of the Enterprise Reporter user who performed the event and the machine name where the event occurred.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center