April 29, 2010 at 9:42 am
Hi there - as described I am getting an error of:
Timeout Expire. The timeout period elapsed prior to completion of the operation or the server is not responding,
However if I click connect again immediately after I connect fine. This is consistent, does anyone else get this? Is there a timeout interval I can set?
Thanks
April 29, 2010 at 11:10 am
Server Properties, Advanced. Remote Login Timeout.
Hope that helps.
You might also want to check the Event logs when this happens to see if they'll tell you anything you don't know.
April 30, 2010 at 8:32 am
What's the database you are connecting to? Is it set to autoclose?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
May 4, 2010 at 10:26 am
The database I am connecting to is a SQL 2005 OLTP DB. The Auto Close is set to false.
May 4, 2010 at 11:15 am
Another question. Are you querying directly through SSMS or through an application or web service?
Connection Timeout properties can hide all sorts of places and not all of them are inside SQL Server.
May 5, 2010 at 4:00 am
It is directly through SSMS.
May 5, 2010 at 4:13 am
How are you running through SSMS? Are you right-clicking an object in the Object Explorer and choosing execute or are you running the code directly in a query window?
We ran into this problem with one of our users. He kept right-clicking a view and hitting execute and that caused his code to time out. When he did the code directly from a query window, though (Select * from MyView), it worked perfectly.
May 5, 2010 at 7:05 am
Sorry I am not even getting to execute code, this error happens when trying to connect to the database engine remotely. I have increased the remote timeout but still get the message, but if I click connect again it connects straight away fine, weird.
May 5, 2010 at 7:22 am
Have you tried using the IP Address to connect? Perhaps you are having DNS issues.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
May 5, 2010 at 11:34 am
Kwisatz78 (5/5/2010)
Sorry I am not even getting to execute code, this error happens when trying to connect to the database engine remotely.
Walk us through the steps you're using to connect. Describe each one in detail.
May 6, 2010 at 5:12 am
I am using the IP address\Instance name to connect already.
Ok the steps are as follows:
1. Launch SSMS on my lcoal machine
2. Select Database Engine to connect to using windows auth and server name of IP\instance name
3. Click connect
4. Get the error - Can not connect to IP\instance name - Timeout expired
5. Click ok to get rid of error
6. Click Connect to try to connect to instance again
7. Connection is successful and I can access my instance
This is consistent whenever I shut down SSMS on my local machine and try to reconnect.
May 6, 2010 at 5:57 am
Are you running a clustered server environment? Does your network use a foundary for passing up connections to the cluster?
We've had issues with our foundary where it would keep routing certain connections to a dead path, but connections would work on another attempt. I don't know enough details about the issue, but that almost sounds familiar.
Another thing to check. Are you sure the Services on the server are set to run Automatically? And that they are running when you initially try to connect on the server?
Does your windows login have an account on the instance or are you part of an AD group that has perms on the server?
May 6, 2010 at 6:04 am
Is anyone else experiencing this problem?
Once you are connected what database are you connected to? Is it a user database or a system database (master, msdb, tempdb, model)? Please check the default database assigned to your login. You can do that with this command in SQL Server 2005/2008:
SELECT
SP.name,
SP.default_database_name
FROM
sys.server_principals AS SP
WHERE
SP.name = '[your login name]' -- this will need to be domain\user if using integrated windows auth.
If your default database is a user database try changing it to master or tempdb with this command:
--if a windows login it must be domain\user enclosed in brackets
ALTER LOGIN [login name] WITH default_database = tempdb
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 13 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply