Home > Report Manager > Troubleshooting the Report Manager > Timeouts

Timeouts

There are various types of Timeouts that can occur during data extraction phase of a report execution. The three most common that can affect the execution of a report and troubleshooting options are described below:

• Connection Timeout - This occurs when Sage Intelligence Reporting cannot connect to the Database System in good time. By default Sage Intelligence Reporting will try to connect for 30 seconds. If there is no response from the Database System then a connection timeout error will occur. To increase this threshold add (or modify) the Key SQLConnectTimeout to the [Publisher] section of the ALCHEMEX.INI file, for example, to increase it to 60 seconds add this key to the Publisher Section:

  SQLConnectTimeout=60.

Note: Setting this value affects all Sage Intelligence Reporting Connections. Setting this value to 0 (zero) will cause Sage Intelligence Reporting to wait indefinitely for Connections to be established.

• Query Execution Timeout - This occurs when Sage Intelligence Reporting cannot execute a SQL statement against the Database System in good time. For some database systems this Execution Timeout is configured within the Database System. It is sometimes referred to as a Query Governor Limit and is usually configured to prevent long running queries from monopolizing the Database System. Either of the following techniques can be used to address the problem :

  • Configure a Timeout threshold at the Container level in the Connector. You will need to do this for all Containers that are being used in Reports that are experiencing Execution Timeouts. See the advanced property Timeout Enquiries After (Seconds) of the container. For more details click here.
  • If a Query Governor Limit (or equivalent configuration option) is available in your Database System then arrange with your Database Administrator (DBA) to configure this value.
• Wait Lock Timeout - These timeouts occur when a query is waiting for another process to release a locked record in a table. Records usually get locked when they are being updated (or edited) in a system. These timeouts cannot usually be avoided by the Database System you are using may provide setting for minimizing occurrences of Wait Lock Timeouts.

Note: The underlying Database System Configuration may override the available Sage Intelligence Reporting Timeout Settings. If this is the case and you continue to experience Timeout problems then please refer the problem to your DBA.