Support Forums - View Thread

View Thread

The following is the text of the current message along with any replies.

Messages 1 to 4 of 4 total

Query timeout with local server, Error #1101

Mon, Sep 26 2011 3:03 AM	Permanent Link
TonyWood	I have a INSERT / SELECT query which takes about 6 minutes when run from ElevateDB manager to a local server (i.e. at 127.0.0.1) to complete successfully. However, when i run the same query programmatically from VB .Net via an ODBCConnection object, I get Error [HY000] [Elevate Software][ElevateDB] ElevateDB Error #1101 The connection to the server '127.0.0.1' has been lost ('Timed out while receiving stream') How can i increase the timeout value ? I see from the EDB doco the default value for a session timeout is just 3 minutes - is this the problem ? What i was hoping to see was a configuration item for a query timeout. Is this a property of the ODBC ? I can see EDBConfig.EDBCfg and log file but these appear to be binary data. How can i read / modify these ? Thanks (again) in advance Tony Wood
Mon, Sep 26 2011 3:11 AM	Permanent Link
TonyWood	Oh yeah - i forgot to say that i'm running EDB 2.05 build 10 on Windows 7
Mon, Sep 26 2011 9:51 PM	Permanent Link
TonyWood	I think i've fixed it ... I've been running edbsvr as a windows service, starting automatically at boot time. Running like this, i was unable to figure out how to configure it, (the EDB icon does not appear in the system tray). I ran it as a normal service and reconfigured to increase the session timeout, and also programmatically set the "TIMEOUT" value in the registry to 900 (15minutes) : SOFTWARE\ODBC\ODBC.INI\<DB_NAME>\TIMEOUT = 900. It seems to be holding up for the longer queries now.
Mon, Oct 3 2011 8:42 AM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Tony, << I've been running edbsvr as a windows service, starting automatically at boot time. Running like this, i was unable to figure out how to configure it, (the EDB icon does not appear in the system tray). I ran it as a normal service and reconfigured to increase the session timeout, and also programmatically set the "TIMEOUT" value in the registry to 900 (15minutes) : SOFTWARE\ODBC\ODBC.INI\<DB_NAME>\TIMEOUT = 900. >> Yes, that is the only option for the ODBC driver. If you use the native ..NET data provider for EDB, you can attach an event handler for the EDBConnection class that will allow you to manage these timeout conditions interactively, asking the user if they want to keep waiting, etc. Please see the OnTimeout event here: http://www.elevatesoft.com/manual?action=viewtopic&id=edb2dac&topic=EDBConnection -- Tim Young Elevate Software www.elevatesoft.com