A.4 Changing Timeout Values

You might encounter report timeout issue because of connection errors. To avoid the report timeout issue, review the following sections:

A.4.1 Executing Reports

If you run reports that return large data sets, the time required for the report execution might exceed the connection timeout setting configured for the data source. Consequently, the report execution times out. To avoid this timeout issue, increase the value of the Timeout attribute for each Connection element before you execute the report. This Timeout attribute is listed in the XML column of the NQRConfig database DataSource table. By default, the TimeOut value is 3600 seconds. A value of 0 indicates no timeout limit and the report query executes indefinitely.

Sample of the XML column content:

<ExtDataSource Name="datasource name" DataSourceType="datasource_type" Description="datasource_desc" DefaultConnection="no_of_default_connections">
 <Connection Name="name" Server="ServerName1" Database="database_name" TimeOut="3600" />
</ExtDataSource>

To change the value of the Timeout attribute that is listed in the XML column of the NQRConfig database DataSource table, do the following:

  1. Open the NRC.ExtDataSource.xml file that is available in the \NetIQ\Reporting Center\Config\ folder.

    NOTE:The NRC.ExtDataSource.xml file opens as Read-only mode. You must change to Write mode to edit the file.

  2. Modify the Timeout attribute value of the <Connection> element based on your report execution time

  3. Check in the NRC.ExtDataSource.xml file by using the following command at the command prompt:

    XMLCheckin.exe <SQL Server named instance> "Path for the xml file"

    For example: XMLCheckin.exe <NQRConfig Database Server> "E:\NRC\NRC.ExtDatasource.xml"

    NOTE:The XMLCheckin.exe file is available in the \NetIQ\ReportingCenter\Utilities folder.

You can also increase the value for the executionTimeout attribute of the <httpRuntime> element, which governs the length of time a request is allowed to run before ASP.NET automatically shuts it down. Add the following <httpRuntime> element within the <system.web> section of the Web.config file, which is available in the \NetIQ\Reporting Center\WebService folder. Set the executionTimout value to match the TimeOut values you set for the <Connection> element.

<httpRuntime executionTimeout="3600"
maxRequestLength="4096"
useFullyQualifiedRedirectUrl="false"
minFreeThreads="8"
minLocalRequestFreeThreads="4"
appRequestQueueLimit="100" />

A.4.2 Loading or Importing Reports

When loading a report or importing a large number of reports, you might encounter a timeout issue. To avoid this timeout issue, increase the value for the TimeOut attribute in the Connection element of the Web.config file on the Web Service website. By default, the TimeOut value is 3600 seconds.

<Connections>
    <Connection Name="Config" Server="ServerName1" Database="NQRConfig" TimeOut="3600" ConnectionType="SQL" />
  </Connections>

You can also increase the value for the executionTimeout attribute of the <httpRuntime> element, which governs the length of time a request is allowed to run before ASP.NET automatically shuts it down. Add the following <httpRuntime> element within the <system.web> section of the Web.config file, which is available in the \NetIQ\Reporting Center\WebService folder. Set the executionTimout value to match the TimeOut values you set for the <Connection> element.

<httpRuntime executionTimeout="3600"
maxRequestLength="4096"
useFullyQualifiedRedirectUrl="false"
minFreeThreads="8"
minLocalRequestFreeThreads="4"
appRequestQueueLimit="100" />