| Author |
Topic |
|
mikhail
Starting Member
12 Posts |
 Posted - 2004-01-22 : 12:51:50
|
| I am using Desktop edition of SQL Server 2000 on my workstation and yesterday start having connection problems to remote servers in the Enterprise manager.The Error message while connection was General Error (PreLoginHandShake()).I've tried all kind of things but nothing worked so I did 2 things: uninstall existing version, reinstalled it and then installed serveice pack 3a. After that I did not notice any changes. Then I used Client Network Utility and created aliases for all remote servers.I made a progress, now I can connect to the servers in the Enterprise Manager.There are still 2 issues remaining:1. Query Analyzer fails when trying to connect with General Error (TCP/IP sockets)2. SQL Server Agent fails to retieve the list of jobs from the remote server... |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-22 : 12:55:11
|
| It sounds like you have a network problem. How fast is the ping to the database servers?Tara |
 |
|
|
mikhail
Starting Member
12 Posts |
Posted - 2004-01-22 : 12:58:01
|
| Network problem would not make sense because I can connect to Servers in the Enterprise Manager. I can not ping servers because they are behind the firewall.Any other ideas ? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-22 : 13:00:58
|
| Yes you can connect using EM, but you aren't able to retrieve the list of jobs. Does it just hang? The error that you are receiving is a network problem error. Both applications are timing out trying to get through the firewall. To allow QA and EM to wait longer for it to connect, go to Tools then Options in QA, then click on the connections tab. Change the login time out to 60 or whatever makes sense for your network. For EM, go to Tools then Options, then advanced tab. Change the login time out value. So you can get around these problems by changing these values, but that doesn't change the fact that your connection to the database server is slow.Tara |
|
|
|
mikhail
Starting Member
12 Posts |
Posted - 2004-01-22 : 13:15:53
|
| Yes, EM just hangs when trying to retrieve the list of jobs.I've changed the login timeout to 100, query timeout to 1000, but still getting the same results.What is strange about the whole situation that data retrieval in the EM while going to the tables/views is exteremely FAST ! |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-22 : 13:52:29
|
| At my last job, I had to change the login timeout to 300 in order to connect to a SQL Server through a firewall. It was quite painful to wait a few minutes just to establish a connection. Once connected though, everything was fast. The point though is that the problem that you are having is outside of SQL Server. Perhaps your network admins can come up with a better solution for you.Tara |
|
|
|
mikhail
Starting Member
12 Posts |
Posted - 2004-01-22 : 13:58:58
|
| I am not sure that I am following you.I am connected now in the Enterprise Manager and data retrieval is fast as I said before.I've tried increasing timeout to 300 as you proposed and no luck.Do you know what is the difference between connection in Query Analyzer and Enterprise manager ?Any other ideas what else may be wrong, my co-worker is having the same problem. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-22 : 14:06:36
|
| Data retrieval is going to be fast. It's the connection that is slow. We had this same problem at my last job. EM could connect but not QA. No I do not know what the differences between them are. I would think that EM would be slower since it does so much when you connect. But obviously, both of us encountered the reverse. Keep increasing your timeout value. Set it to 1000. Are you using the same alias in both EM and QA? Same authentication?Tara |
|
|
|
mikhail
Starting Member
12 Posts |
Posted - 2004-01-22 : 14:30:59
|
| Tara wrote:>Keep increasing your timeout value. Set it to 1000. I did , now I get the following error while clicking on the Jobslink in EM.Error: 0. Server has been disconnected. You must reconnect to perform this operation.Traying to reconnect gives the same result.BTW I am using the same alias in QA as in EM.ThanksMikhail |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-22 : 14:33:56
|
| Try connecting to the SQL Server using osql.exe. osql.exe is much lighter than EM and QA, so it should be able to connect quicker. Let me know what error that you get if any.Tara |
|
|
|
mikhail
Starting Member
12 Posts |
Posted - 2004-01-22 : 15:06:07
|
| I've tried connecting and did not have any problems. I ran the simple query and return back results.Any clues ? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-01-22 : 15:17:53
|
| The fact that osql.exe is working fine points to a network problem, a slow network problem. EM and QA do a lot more when connecting to a SQL Server than osql.exe.So your options are use osql.exe for SQL Server work or contact your network admin to figure out why it is so slow. Maybe he/she has a different solution for connecting to the box.Tara |
|
|
|
|
Connection Failure and more...