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 |
|
tolhurma
Starting Member
3 Posts |
 Posted - 2008-04-01 : 17:04:58
|
| I am running a failover cluster on 2 servers with Windows 2003 Ent (no service pack) [win2k3]and SQL 2000 SP3 [sql2k].I am executing a set of stored procedures that take approximately 3 hours to run (directly on the server) and have twice received the error: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).Server: Msg 11, Level 16, State 1, Line 0General network error. Check your network documentation.The error has occurred at different times into the execution.The Agent is off and users are denied access to the server.The process has been running fairly happily for a number of years.Can anyone shed any light on this? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-04-01 : 17:10:55
|
| Something is causing your connection to be disconnected. There isn't much that we can do from the SQL Server side to troubleshoot. Do you have any network or server admins that can assist you with network connectivity?Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
tolhurma
Starting Member
3 Posts |
Posted - 2008-04-01 : 18:45:08
|
| Why would network connectivity come into it? The sp is being executed directly on the server using a sql account. My only use of the network is mstsc to connect?I have checked with the service providers and there are no known network issues.Trawling the net there seem to be many refernces to this problem - I can't find any that match our setup though (and the server is not busy as I run the task) |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-04-01 : 18:53:37
|
| Even though you are executing it directly on the server doesn't mean that it doesn't go out to the network during the connect. I think you'd have to refer to 127.0.0.1 in order to avoid that.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
tolhurma
Starting Member
3 Posts |
Posted - 2008-04-01 : 19:03:10
|
| ok. sounds like your on to something. If I try to connect to 127.0.0.1 in QA it fails (never tried that before). If I try to connect to [local] it tries to connect to the current active node (bearing in mind I am using terminal services to connect to the virtual cluster) - that fails. Can I terminal service straight into the active node and use sql or will that upset the cluster? Thanks for your help... |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-04-01 : 19:05:50
|
| Well you can't use 127.0.0.1 on a cluster as the instance isn't listening on that. But my point had to do with networking concepts.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
General Network Error