We are experiencing an issue with Generic ODBC Data Sources in TimeXtender 20.10.74.64 on SQLTX01.
Environment
- TimeXtender version: 20.10.74.64
- Repository/Application: 20.10.74.64
- Server: SQLTX01
- OS: Windows Server 2019 Datacenter
- SQL Server: Microsoft SQL Server 14.0.3520.4 NT x64
- TX build: 64 bit
Initial situation
We originally noticed the issue on a PostgreSQL source that is accessed through an SSH tunnel.
The PostgreSQL ODBC connection itself works correctly when tested directly in the ODBC Data Source Administrator.
Example:
- server:
127.0.0.1 - port:
5433 - ODBC test from Windows ODBC Administrator: successful
At first we suspected a PostgreSQL / tunnel issue, but further testing suggests this is not the case.
What happens in TimeXtender
The issue occurs inside the Edit Generic ODBC Data Source dialog.
There are two scenarios:
1. Opening the DSN dropdown
When we open the Generic ODBC Data Source dialog and click the dropdown to show available System DSNs, TimeXtender immediately fails.
So the failure already occurs while TimeXtender is trying to enumerate the available ODBC DSNs/providers.
2. Clicking “Test Connection”
Even if a DSN is already selected, clicking Test Connection in TimeXtender also fails immediately.
Error message
The error shown by TimeXtender is:
Communication with execution engine failed
No response from Execution Engine
Relevant stack trace
When opening the DSN dropdown, the stack trace includes:
TimeXtender.DataManager.AddEditOdbcDialog.cbProviders_DropDown(Object sender, EventArgs e)
This strongly suggests the failure happens when TimeXtender tries to retrieve the list of available ODBC providers / DSNs.
When clicking Test Connection, the error includes:
TimeXtender.DataManager.AddEditDataSourceCommand`2.Dialog_TestConnection(Object sender, EventArgs e)
In both cases the root error is:
No response from Execution Engine
Module: ExecutionEngineLogic
System.Exception
at ExecutionEngineLogic.Communication.ExecutionEngineServer.StartRequest(...)
Important observations
- Other non-ODBC connections in TimeXtender are working normally.
- This is not limited to PostgreSQL.
- We tested the same behavior with a SQL Server ODBC DSN, and TimeXtender shows the exact same error.
- Therefore this does not appear to be a remote database issue.
- It also does not appear to be a PostgreSQL-specific issue.
- It appears to be related to TimeXtender Generic ODBC handling / Execution Engine interaction with local ODBC enumeration.
Additional notes
- There has been no recent TimeXtender update on our side.
- The server has already been rebooted.
ExecutionEngine_x64.exeappears very briefly and then disappears.- We do not see a useful related error in Windows Event Viewer.
- Direct ODBC tests from the Windows ODBC Administrator succeed.
Our conclusion so far
Based on the tests above, the issue seems to occur before an actual database connection is made.
It looks like TimeXtender fails when:
- enumerating local ODBC DSNs/providers, or
- starting the Execution Engine for Generic ODBC handling.
Because the same issue occurs with both PostgreSQL and SQL Server ODBC DSNs, we believe this is likely a Generic ODBC / Execution Engine issue in TimeXtender, rather than a source-specific connectivity issue.
Question
Has anyone seen this behavior before, where:
- opening the System DSN dropdown in a Generic ODBC Data Source already causes
“Communication with execution engine failed / No response from Execution Engine” - and the same happens for Test Connection
- while the ODBC DSNs themselves test successfully in Windows?
Any guidance on:
- Generic ODBC troubleshooting in TX 20.10
- Execution Engine diagnostics for ODBC enumeration
- known issues with ODBC provider enumeration
would be appreciated.
