Timeout Settings for Run Time

If the data adapter service sends a large amount of data (for example, for a dimension), and the amount of time it takes for the data to be transmitted to the server is longer than the default transmission timeout, a run-time error occurs. The error appears in the Logger. You can adjust the timeout by editing the DasClientSendTimeoutSeconds setting in the IntelligenceService.exe.config file. This setting has a default value of 1500 seconds. If you configure this setting to use a value lower than 1500, the setting will automatically be adjusted back to 1500. If you configure this setting to use a value greater than 1500, the setting will never be automatically adjusted.

The amount of time that the BI Gateway software allows run-time database transformation and merge commands to execute is called the query timeout, which is measured in seconds. One scenario in which the query timeout may occur is if you edit a dimension that has a lot of associated records and the edit causes a schema change. Another scenario is if the dimension tables have more than eight million records, you may notice query timeout run-time errors in the Logger related to query execution.

You can adjust the timeout by editing the QueryTimeout setting in the EMIRuntimeConfigurator.xml file. This setting has a default value of 9000 seconds. If you configure this setting to use a value lower than 9000, the setting will automatically be adjusted back to 9000, because 9000 is the minimum value that is accepted by BI Gateway. If you configure this setting to use a value greater than 9000, the setting will never be automatically adjusted.

Note: You must restart the Intelligence Runtime service in order for this setting to take effect after changing QueryTimeout setting in the EMIRuntimeConfigurator.xml file.