How to resolve when the build fails with "Execution Timeout Expired"
Learn how to fix build failures caused by the "Execution Timeout Expired" error during data imports from SQL Server. This guide walks you through common causes—like long-running queries or network issues—and how to adjust timeout settings for a successful import.
Introduction:
This article provides guidance for extending the execution timeout value in the DotNet SQL Server connector configuration to resolve the build failure with "Execution Timeout Expired. The timeout period elapsed prior to completion of the operation, or the server is not responding."
Step-by-Step Guide:
The “Execution Timeout Expired” error occurs when a query takes too long to execute on the data source side. The DotNet SQL Server connector sets the timeout value to 300 seconds as the default. Old releases such as Sisense 7.4 set the timeout value to 60 seconds as the default. You can extend the timeout value with the following steps.
- Stop Sisense.CLRConnectorsContainer Windows Service
- Open “C:\Program
Files\Sisense\DataConnectors\DotNetContainer\Connectors\MS-SQL\Sisense.Connectors.MsSqlConnector.dll.config” with a text editor such as Notepad - Find the Timeout parameter like the one below in the file:
<add key="Timeout" value="300" /> - Update the value to a sufficient amount of time for executing the failed query
- Save the file
- Start Sisense.CLRConnectorsContainer Windows Service
Conclusion:
By setting the timeout value to a sufficient amount of time for the query to be executed on SQL Server and receive results, it prevents the build failure due to the "Execution Timeout Expired” error.
Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.
