| Author |
Topic |
|
homebrew
Posting Yak Master
114 Posts |
 Posted - 2007-11-02 : 16:37:02
|
| I just did a 2005 "In-Place" upgrade to a 2000 server yesterday, and now we're getting intermittant time-out errors trying to connect via SQL Server Management Studio. Sometimes we connect instantly, then if I try again 10 minutes later, it might time-out. No problems with our other 4 SQL 2005 servers (2 were just upgraded, 2 are native 2005). No timeouts so far when logged on to the server directly, just when logging in from our desks.It's set to TCP\IP only (removed named pipes), but can't think what else might be the problem. Any ideas ?One little thing I just noticed while comparing to another server: In the console, a "good" server has the little green arrow on the server & SQL Agent icons, while the "problem" server is connected, but there is no green arrow. If I log on the server directly and open SQL, I get the green arrows. Is that trying to tell me something about the connection ?? |
|
|
anonymous1
Posting Yak Master
185 Posts |
Posted - 2007-11-02 : 17:14:48
|
| is there anything in your sql server logs? does it occur for all work stations? is the sql server registered by IP or computer name? |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-11-02 : 22:48:57
|
| Try connect with ip address and port number. By the way, did you use windows or sql authentication? |
|
|
|
Kristen
Test
22859 Posts |
|
|
homebrew
Posting Yak Master
114 Posts |
Posted - 2007-11-03 : 12:14:59
|
| No, I didn't set 90 compatibility or re-index. Is that recommended after upgrading ? That wouldn't help the problem of the initial connection timing-out, would it ? |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-11-03 : 20:21:14
|
| No, but helps for query performance. You didn't tell us how to connect to sql yet. |
|
|
|
homebrew
Posting Yak Master
114 Posts |
Posted - 2007-11-03 : 21:47:52
|
| We just connect with SQL Server Management Studio (Enterprise Manager 2000 replacement). However we also got a timeout once while connecting with the application itself. It's sporadic, times-out 20% of the time, which is puzzling. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-11-03 : 21:50:27
|
| Again, did you try connect with ip address and port number? Use windows or sql authentication? |
|
|
|
homebrew
Posting Yak Master
114 Posts |
Posted - 2007-11-03 : 22:01:57
|
| Sorry for the incomplete answer.I just tried to ping the server & it timed out, although I could remote desktop into it, so it is up & running. Normally, I have been connecting with SQL authentication, although timeouts have happened with SQL & Windows authentication, and also worked fine with both. I have been using the server name, in SQL Mgmt Studio, but just tried IP address there instead & it also timed out. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-11-03 : 22:09:23
|
| If you get a timeout on the ping or if the IP address does not work in SSMS, then you need to contact the network admins as the issue is not with SQL Server.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
homebrew
Posting Yak Master
114 Posts |
Posted - 2007-11-03 : 22:23:38
|
| I just tried another ping (15 minutes later) and it worked fine. Hmmm |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-11-03 : 23:07:57
|
| You should get your network guys involved in this case, maybe nic setting doesn't match switch's or so. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-11-04 : 02:19:50
|
| "Is that recommended after upgrading?"It would be nice if you read the link I went to the trouble of finding for you, instead of asking me to retype the contents of it here. If it raises questions, or fails to help, I'll be happy to try to assist further."I just tried another ping (15 minutes later) and it worked fine. Hmmm"What did your network admins say?Kristen |
|
|
|
homebrew
Posting Yak Master
114 Posts |
Posted - 2007-11-05 : 09:35:46
|
| RESOLUTION: There was a duplicate IP address caused by dhcp after upgrading to Windows Server 2003. It has been removed, so that should resolve it.Thanks to everyone for all the help & ideas. |
|
|
|
|
Timeout connecting to upgraded 2005 server