Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-09-05 : 07:49:15
|
| Prabhu.S. writes "Hello,MSSql Server Version : 7.0 OS : Win NT (Service Pcak 4)In the SQL Enterprise Manager, I am trying to open my DB Server Group(Under the Server Group)I am getting the following error Error Message:--------------"A connection could not be established to My DB server - Timeout Expired"But if i press refresh then connection is getting established and I'm able to see everything under my DB server Group. Also, i have checked everything in my SQL server registration and everything is perfectly ok. Can you please advise me how to rectify this problem. Is there anything related to ODBC?? .. Please advise me.Thanks & regards,Prabhu.S." |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2003-09-05 : 08:45:30
|
| Tools -- options -- Advanced. Try raising the login query timeout value. Otherwise it is difficult to say. Maybe your network / server is under heavy load or something?-------Moo. :) |
 |
|
|
mohdowais
Sheikh of Yak Knowledge
1456 Posts |
Posted - 2003-09-05 : 11:37:41
|
You know what? I have the same problem at work. While connecting to the live server neither Query Analyzer nor Enterprise Manager will connect the first time around (I get a connection timeout), but if I try again it gets connected in a couple of seconds. Nothing I can't live with, but if somebody's got a solution I'd be happy  Owais
Make it idiot proof and someone will make a better idiot |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-09-05 : 11:51:18
|
| To rectify this problem, contact the Network Administrators. The problem is with the communication to the SQL Server box, which means that it is most likely network related or maybe the SQL Server is under some stress, so check that out too.Tara |
|
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2003-09-05 : 12:27:47
|
we get something similiar in our area.....and it's to do with the network routing tables....but our admin guys say nothing changed.. A work-around we've used is to specify the server name using the ip address, rather than the 'alias' |
|
|
|
|
|
|
Getting an error - Very Urgent