At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.
SQL Server Timeout Issue
I am trying to debug an app on my machine which is running Windows 7 64, MS SQL 2008 Developer Edition and Visual Studio 2008.
When I try to make a connection through VB to the SQL database I kept getting a timeout error. After trying a number of things I then tried to make an ODBC connection to the SQL DB and got the same timeout error - HYT00.
I have checked that all SQL and associated services are running, "Shared Memory", "TCP/IP" and "Named Pipes" are all enabled but I am out of ideas. I have tried calling the machine by its name, its IP address and '.' none of which make any difference.
I use SQL Server authentication to log into my DB and am happily able to log in and to work on my db through SQL Management Studio using the same login I am trying for ODBC.
Any ideas?
Thanks
When I try to make a connection through VB to the SQL database I kept getting a timeout error. After trying a number of things I then tried to make an ODBC connection to the SQL DB and got the same timeout error - HYT00.
I have checked that all SQL and associated services are running, "Shared Memory", "TCP/IP" and "Named Pipes" are all enabled but I am out of ideas. I have tried calling the machine by its name, its IP address and '.' none of which make any difference.
I use SQL Server authentication to log into my DB and am happily able to log in and to work on my db through SQL Management Studio using the same login I am trying for ODBC.
Any ideas?
Thanks
Asked:
5-
4
-
2
- +1
1 Solution
Within ADO, the developer can set:
1. connection timeout (default 15 seconds)
if the connection cannot be established within the timeframe specified
2. command timeout (default 30 seconds)
cancellation of the executing command for the connection if it does not respond within the specified time.
These properties also support a value of zero, representing an indefinite wait.
Here is some example code:
1. connection timeout (default 15 seconds)
if the connection cannot be established within the timeframe specified
2. command timeout (default 30 seconds)
cancellation of the executing command for the connection if it does not respond within the specified time.
These properties also support a value of zero, representing an indefinite wait.
Here is some example code:
Dim MyConnection as ADODB.Connection
Set MyConnection = New ADODB.Connection
MyConnection.ConnectionTimeout = 90
MyConnection.Open
Set MyConnection = New ADODB.Connection
' set strMyConn
MyConnection.Open strMyConn
Set myCommand = New ADODB.Command
Set myCommand.ActiveConnection = MyConnection
myCommand.CommandTimeout = 90
you also try changing the request time out in page by:-
on page load.
Server.ScriptTimeout = 1800 ' in seconds
on page load.
A nice approach I use a lot is to create a new txt file on your desktop, and once it is created, replace the txt extension with udl.
You can then double click this udl file, and create your connection properties using the familiar wizard.
Hopefully you can play around with all of the providers listed etc, and other connection properties until your connection is successful.
If you then save and re-open the udl file in a text editor, it will show you the connectionstring you need to use within VS.
If you can't connect using any of the providers, then you definitely have something configured wrong in server configuration manager.
I hope this helps.
L
You can then double click this udl file, and create your connection properties using the familiar wizard.
Hopefully you can play around with all of the providers listed etc, and other connection properties until your connection is successful.
If you then save and re-open the udl file in a text editor, it will show you the connectionstring you need to use within VS.
If you can't connect using any of the providers, then you definitely have something configured wrong in server configuration manager.
I hope this helps.
L
rajvja, i know that increasing the time out is not a good solution
but sometimes in case of large database, heavy operations or slow network
it can be changed for a particular task to suit our requirements.
but sometimes in case of large database, heavy operations or slow network
it can be changed for a particular task to suit our requirements.
Everything is local, there is no network or heavy usage and the db is very small. I have tried fiddling with the timeout anyway but it makes no difference
Is this using ODBC still?
Just out of interest, why do you want to use ODBC? It is quite an old protocol.
Does the UDL connection still time-out if you pick the MS OLE DB Provider for SQL Server?
Thanks,
Just out of interest, why do you want to use ODBC? It is quite an old protocol.
Does the UDL connection still time-out if you pick the MS OLE DB Provider for SQL Server?
Thanks,
It may also be worth downloading the latest OleDB and ODBC Drivers for SQL 2008 from here:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c6c3e9ef-ba29-4a43-8d69-a2bed18fe73c
Regards,
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c6c3e9ef-ba29-4a43-8d69-a2bed18fe73c
Regards,
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
Can you try configuring a data source in design view and check the Test Connection. If succeeds, try to copy the connectionstring and use the same in your application.