Post reply

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).Server: Msg 11, Level 16, State 1, Line 0General network error. Check your network documentation.Connection Broken

  • May 17, 2005 at 5:03 am

    #163590

    Iam getting this problem for particular query,when every i run that query iam getting problem like this

     

    [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).Server: Msg 11, Level 16, State 1, Line 0General network error. Check your network documentation.Connection Broken

  • May 17, 2005 at 11:48 am

    #559334

    You lost your connection to the server.

  • May 23, 2005 at 6:29 am

    #560474

    Thanks Steve..

    But why.. this connection brokes when that particular Query runs..if i not run that particular query..DB will not disconnect

  • May 23, 2005 at 6:56 am

    #560480

    Not sure what query you're running -

    what service pack do you have ?! Apparently this was a known bug sometime back that was fixed with sp4 (I think!)...







    **ASCII stupid question, get a stupid ANSI !!!**

  • May 23, 2005 at 9:33 pm

    #560651

    I have seen this sort of error happen occassionally even though there appears to have been no actual loss of network connectivity to the server. It was happening when using a wireless connection (802.11) from the workstation. Running the same query with a wired network did not cause the error.

    I never really worked out what was causing the problem but you could try change the default protocol that your workstation is using (e.g named pipes instead of TCP/IP

  • May 24, 2005 at 1:17 pm

    #560836

    It seems like more information is needed for any one to be helpful.

    Where are you running the query from?

    Is this a distributed query?

    Can you give a sample?

  • August 4, 2005 at 3:55 pm

    #579874

    You get this error if you try to insert data from one  datatype to another. for example nvarchar(50) to varchar(50). Changing datatype to nvarchar(50) should solve the problem.

  • November 1, 2006 at 9:22 am

    #669242

    I have the same issue but it had nothing to do with the changing of datatypes. If you remove the distributed query it works however if you keep it and change the select statement to select top 10* lets say it will work to.

    2 work arounds I have found are selecting all data into table variable the other option is to create a UDF.

  • November 1, 2006 at 11:43 am

    #669284

    better post your query and connection settings ...

    Kindest Regards,

    Vasc

  • November 2, 2006 at 12:31 pm

    #669594

    This forum is for SSC.com site suggestions...

    Please post your question in the appropriate forum.

    Perhaps this one:

    http://www.sqlservercentral.com/forums/messages.aspx?forumid=20

    Not only does it help keep the site clean and stand a far better chance of getting answered in a timely fashion, but it also helps other users by showing this problem and solution under its logical heading...

    Makes for easier searching, etc.

    Sorry I can't be of more help with your problem.


    Enjoy!

    A Brown

    Manage all of your backups in one simple job using this script.

  • July 17, 2007 at 2:21 am

    #719918

    Hi,

    I am getg similar error when making DSN.Win2k3 box to Sql server2000.

    ******************************

    Connection Failed

    SQL STATE:'01000'

    Sql Server Error:10054

    [MICROSOFT][ODBC SQL DRIVER][TCP/IP SOCKETS]]ConnectionRead recv().

    connection failed.

    SQL STATE:'08S01'

    Sql Server Error:11

    [MICROSOFT][ODBC SQL DRIVER][TCP/IP SOCKETS]]General Network error.Check your netweok documentation.

    ********************

    From other server its getting connected.

    Is it something to with Network card?

    Help highly appreciated.

    Sudeep

     

     

     

  • April 1, 2011 at 11:35 am

    #1306629

    It's due to a server configuration named "query wait", which states the # of seconds your query executer will wait before breaking the connection.

    By default, it is set to -1. Which means 25 times the query cost. That is, if a query cost is estimated to run in 2 seconds, the time it will wait at most is 50 seconds. Normally that's enough, but depending on the server load and thousand other possibilities, it might not be enough.

    The fact u guys say it works perfect for a top 10 * limit of rows only proves it. Coz the cost of the query for a top 10 reduces considerably.

    The solution is seting an explicit # of seconds for any query to last before connection is broken. Depending on how much time u think ur query will need, u'll need to set that time in seconds.

    Say 200,000 seconds is a little over 2 days, and in my experience it covers any heavy query, unless u need more time than that, of course, you can customize it to whatever ur needs are.

    This is the code for changing the query wait option in the server.

    -- this one lets u update query wait, in case u don't have it enabled

    sp_configure 'show advanced options', 1

    go

    reconfigure with override

    go

    -- and this one does the trick

    sp_configure 'query wait', 200000

    go

    reconfigure with override

    go

    To change it back to normal, just set the seconds parameter to -1.

    Hope it is of help.

    Meer

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply