General Network Error Check Your Network Documentation Sql
Contents |
24, 20082 0 0 0 This is a proper netwrok [dbnetlib][connectionread (recv()).]general network error. check your network documentation. error and has nothing to do with the dbnetlib connectionwrite (send()). general network error. check your network documentation coding if any of your jobs/queries/packages fail with this message. Please refer the communication link failure sql following article for the workaround. http://support.microsoft.com/kb/942861/en-us Another work around we tried and succeeded in our project was as follows: There is something
Microsoft Sql Server Native Client 10.0 Communication Link Failure
called Network Speed setting which is usually set toAUTO or a fixed value. You can check this from Start->Control Panel->Network Connections->Local Area Connection->Properties->Configure->Advanced->Speed &Duplex property. Change it to 100 MBPS full or whatever value that matches the configuration of the n/w port on 08s01 microsoft odbc sql server driver communication link failure the switch side. It solved the issue for us.
Comments (2) Cancel reply Name * Email * Website General Network error. Check your network documentation. | Coded Style says: December 24, 2008 at 2:08 am PingBack from http://www.codedstyle.com/general-network-error-check-your-network-documentation/ Reply Abdul Hadi says: September 7, 2015 at 9:32 pm If some one using programming language and facing this error, then use timeout method (e.g. for C# and VB.Net it is SqlCommand.TimeOut = 600). it will give extra time for your transaction process. Reply Follow UsArchives January 2011(1) July 2010(1) June 2010(1) May 2010(1) January 2010(1) December 2009(1) November 2009(2) August 2009(2) July 2009(1) March 2009(1) All of 2011(1) All of 2010(4) All of 2009(7) All of 2008(7) Privacy & Cookies Terms of Use Trademarks © 2016 Microsofthere for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business error [08s01] [microsoft][sql native client]communication link failure Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation
Communication Link Failure Sql Server 2012
Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just
Sqlstate 08s01 Sql Server
like you, helping each other. Join them; it only takes a minute: Sign up General network error after a night of inactivity up vote 3 down vote favorite 1 For some time now our flagship application has been https://blogs.msdn.microsoft.com/ramoji/2008/12/24/general-network-error-check-your-network-documentation/ having mysterious errors. The error message is the generic [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation. This is reliably reproduced by leaving the app open for the night and resuming work in the morning. Since it's a backend server app this is a normal scenario. The funny thing is - we've migrated from SQL Server 7 to 2000 to 2008 and the issue is present on all of them. But what seems to matter http://stackoverflow.com/questions/3211625/general-network-error-after-a-night-of-inactivity is the OS on which we run the app. On WinXP it works fine, on Vista/7 it fails. So the problem is at the client end. The results of Google on the error message cover a very wide spectrum of different causes (since this is a very generic error) and none of the scenarios found there are similar to ours. So perhaps someone around here will know what the problem is in our case? sql-server general-network-error share|improve this question asked Jul 9 '10 at 10:10 Vilx- 49.8k57194330 Does your app keep a single SQL connection open for the lifetime of the app? –Chris Bednarski Jul 9 '10 at 10:34 @Chris Bednarski - I think so, I'm not familiar with that part. –Vilx- Jul 9 '10 at 11:22 add a comment| 2 Answers 2 active oldest votes up vote 5 down vote You should be able to reproduce this error condition on demand by: 1. Opening a database connection (in your client application) 2. Unplugging the network cable 3. Plugging network cable back in (wait until the network connection is restored) 4. Using the previously opened connection to query the database As far as I can tell from experience, client side ADO code is not able to consistently determine if an underlying network connection is actually valid or not. C
however, all suggested fixes have failed to work for me. I've tried setting POOLING=FALSE. I've also tried setting CONNECTION RESET=FALSE. Although both of these have allowed me to https://www.sitepoint.com/community/t/the-famous-general-network-error-check-your-network-documentation-error-message/1723 keep a connection open for slightly longer, after a while I would get the familiar "General network error. Check your network documentation." error message. It seems that, in general, SQL 7.0 / ADO .NET http://www.itjungles.com/general-network-error-check-your-network-documentation.html does not like it when you keep connections open for more than a half hour, even if you are constantly using that connection. The only way that I've been able to deal with communication link the situation is to occasionally close the connection and open it again. Kind of kludgey, but it's the only fix that has worked. Does anybody else have a suggestion? rbutler 2004-09-15 16:26:40 UTC #2 Afro_Blanca said: It seems that, in general, SQL 7.0 / ADO .NET does not like it when you keep connections open for more than a half hour, even if you are constantly communication link failure using that connection. The only way that I've been able to deal with the situation is to occasionally close the connection and open it again. Kind of kludgey, but it's the only fix that has worked. Does anybody else have a suggestion? I probably won't be too much help, but I was confused by your statement of leaving the connection open for more than half an hour. In your code you should do clean up, i.e., if you opening a connection to a db with a dataReader object, then you should follow this pretty much to the "T". Dim objConn as New OleDbConnection("Some connection string here") Dim objCmd as OleDbCommand Dim objDR as OleDbDataReader objCmd=New OleDbCommand("SELECT * FROM Table_Name", objConn) objConn.Open() objDR=objCmd.ExecuteReader() dgDataGrid.DataSource=objDR dgDataGrid.DataBind() objDR.Close() 'close the datareader object objConn.Close() 'close the connection This way, as soon as the page queries the db for the required data, it closes the DataReader object and Connection, therefore, elminiating the worry about having the connection open for any amount of time which leads to db server strain. This probably has led to more confusion, hopefully not. miseldine 2004-09-15 21:17:01 UTC #3 Should the SqlConnection class disconnect on disposal when garbage collected?
TipsBlackBerry TipsDesign TipsFirefox TipsiPad TipsiPhone TipsJoomla TipsInternet Explorer TipsSmartPhone TipsMicrosoft Excel TipsMicrosoft Word TipsMicrosoft PowerPoint TipsOutlookWindows Phone 7Palm TipsWeb HostingSamsung TipsHTC TipsMOTOROLA TipsNokia TipsSearch Engine OptimizationElectronic AccessoriesSocial MediaInternetPrintersWindows PhoneWeb DevelopmentArticlesGeneral ArticlesReal Estate FormsRemote ControlsOperating SystemWindows VistaWindows 7Windows ServerWindowsOS X Tweet Author: Jenny Nguyen General network error. Check your network documentation Tweet You are getting this error while your code is retrieving data from the database. General network error. Check your network documentationORTimeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding This error generally occurs as the result of the program request large amount of database from the database. The default timeout for the connection is 30 seconds. Once the connection elapse over these 30 seconds you will get a timeout expired error. To fix this issue normally you can do one of two things. 1. You can set the timeout setting in the config file. Although this does not always work.