In SQL Server, connectivity problems can cause a 'Timeout Expired' message to appear in various forms and from different sources, including Microsoft SQL Server Management Studio, ADODB, ODBC,.NET, VB, and other types of scripts and applications.

Download free youtube. In Microsoft Access, when you open a pass-through query to a SQL Server 2000 or SQL Server 2005 database, sometimes the query times out. Usually for me this happens when the database is very large. The error message is: ODBC--call failed.

[Microsoft][ODBC SQL Server Driver]Timeout expired (#0) You can set the timeout interval for ODBC connections in the registry. It is a setting for the Microsoft JET 4.0 engine, which is the database engine that Access 2003 uses. (When you create a new ODBC DSN, and see all those drivers listed that are version 4.00 and contained in ODBCJT32.DLL -- those drivers are part of JET and likely came with MDAC.) The QueryTimeout value lives in the registry at HKEY_LOCAL_MACHINE Software Microsoft Jet 4.0 Engines ODBC The default value is 60 seconds. You can increase the timeout setting, or change it to 0 so that queries will never time out.

Follow these steps: 1. Close Access. Start --> Run 3. In the Open field, type regedit and click OK to run the Registry Editor.

Expand HKEY_LOCAL_MACHINE. Expand Software.

Expand Microsoft. Continue navigating to Jet 4.0 Engines ODBC folder.