General Network Error Sql Server 2008 R2
Contents |
here 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
Communication Link Failure Sql
the company Business Learn more about hiring developers or posting ads with us Stack Overflow dbnetlib connectionread (recv()). general network error. check your network documentation Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of microsoft sql server native client 11.0 communication link failure 4.7 million programmers, just 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
Dbnetlib Connectionwrite (send()). General Network Error. Check Your Network Documentation
now our flagship application has been 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
Communication Link Failure (sql-08s01)
all of them. But what seems to matter 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
Server TCP Chimney Offload transfers network traffic workload processing from the CPU to a network adapter that supports TCP Chimney Offload. This feature was introduced with Windows Server 2003 SP2, and it was called the Microsoft communication link failure sql server 2012 Scalable Networking Pack (SNP). Since Windows Server 2008, these features are a base
Error [08s01] [microsoft][sql Native Client]communication Link Failure
part of these operating systems, so they no longer go by this name. To utilize this feature, the network adapter sqlstate 08s01 sql server (and driver) must support this feature, and both the operating system and the network adapter must have this setting enabled. This feature is not suitable for all applications. Microsoft says (at http://technet.microsoft.com/en-us/library/gg162709%28v=WS.10%29.aspx): Because of http://stackoverflow.com/questions/3211625/general-network-error-after-a-night-of-inactivity the overhead associated with moving TCP/IP processing to the network adapter, TCP Chimney Offload offers the most benefit to applications that have long-lived connections and transfer large amounts of data. Servers that perform database replication, function as file servers, or perform backup functions are examples of computers that may benefit when you enable TCP Chimney Offload. With the different operating systems versions, this feature is by default http://www.sqlsolutionsgroup.com/tcp-chimney-offloading/ in different states: Windows OS Default state of TCP Chimney Offload Windows Server 2003 enabled Windows Server 2008 disabled Windows Server 2008 R2 automatic Windows Server 2012 disabled With all of these changes to the OS, which setting should we use for SQL Server? In general, for all of these operating systems, I recommend that TCP Chimney Offload be disabled – because you can see odd connectivity problems in any other state. Notice in the above quote that Microsoft says that this feature is best used for applications with long-lived connections that transfer large amounts of data - hopefully your OLTP database is performing lots of short-lived connections and they are not transferring large amounts of data (if they are, contact us… we can help you with that!). Some of the error messages that you can encounter are: [Microsoft][ODBC SQL Server Driver][DBNETLIB] General Network error. Check your network documentation ERROR [08S01] [Microsoft][SQL Native Client]Communication link failure System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) These errors are not exclusive to having problems with the TCP Chimney Of
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL http://www.sqlservercentral.com/Forums/Topic258457-149-1.aspx Server 2005 » SQL Server 2005 General Discussion » [DBNETLIB][ConnectionRead (recv()).]General... [DBNETLIB][ConnectionRead https://community.spiceworks.com/topic/543813-connectionread-errors-in-odbc-to-sql-server (recv()).]General network error. Check your network documentation Rate Topic Display Mode Topic Options Author Message RobboRobbo Posted Tuesday, February 14, 2006 7:24 PM Forum Newbie Group: General Forum Members Last Login: Sunday, May 10, 2009 2:54 AM Points: 4, Visits: 3 I have a 3rd party application communication link that is reading tables from SQL Server 2005 Express. Last night I set the program running on a continuous loop that reads values from a few tables, and updates a "heartbeat" record every few seconds - nothing else. This morning I found that after running for about 4 and a half hours it crashed with the following message:Number = 0x80004004Source communication link failure = Microsoft OLE DB Provider for SQL Server Description =[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.SQL State = 08S01NativeError = 11I am running it on a machine operating on Windows XP Professional SP2 and the version of SQL Server 2005 I am running is 2005.090.1399.00. The 3rd party application is running on the same machine as SQL Server. The only systems that interrogate the table are:1. The main program thread of the 3rd party application that does the work mentioned above.2. A MS Access front end that interrogates some of the tables (linked) once every 5 seconds using an On Timer Event3 There are 8 other threads running that are linked to the database on the 3rd party application but, when the application is idling as it was overnight, they do not interact with SQL tables at all.There are a total of 7 tables, the largest having 99 records.I have no idea what this message means or what to do to prevent it from happening. I chose SQL Server because I thought it was going to
system for their student records, admissions, and recruiting. Reverse Proxy Public Web Servers Give our web servers a more robust network backbone. Server Room Refresh long overdue update to our server room TECHNOLOGY IN THIS DISCUSSION Microsoft SQL Server 2012 Microsoft SQL Server 2005 Join the Community! Creating your account only takes a few minutes. Join Now I have an Access database (composed of one table and some reports) that I migrated to SQL Server using the Access "Move Data" wizard. I can read/write to it just fine from the custom in-house software with no errors. It's SQL Server 2008 R2. Everything is default - since it was just one table I didn't change anything but permissions. I connect to it via ODBC in Access. If I leave the table open when viewing the data, I get the following error: ODBC - Call Failed. [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()). (#10054) [Microsoft][ODBC SQL Server Driver][DBNETLIB]General Network Error. Check your network documentation. (#11) [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()). (#10054) [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation. (#11) I then have to close and reopen Access to reconnect. There are three databases on this SQL Server - our ERP, our CRM, and this single table database. The ERP and CRM never have given this error when viewing data for a table in Access. Just this single table db. There are no network card issues in event viewer for either the workstation or the server. Any suggestions on where to start with this? I'm testing out moving this database to SQL Server. I haven't done it before, so there may be something obvious I'm missing. Edited Jul 21, 2014 at 2:51 UTC Reply Subscribe RELATED TOPICS: ODBC headaches... Cannot talk to SQL Server Unable to connect to SQL server remotely SQL Server Virtualization   5 Replies Tabasco OP IPX Dave Jul 21, 2014 at 4:57 UTC Hmm, have you checked to make sure that the account you are on has the appropriate permissions to access that db? 0 Serrano OP Marcos_Julio_ Jul 21, 2014 at 5:29 UTC - Try to create some user to that DB, using SQL Authentication. - Grant Role Members to the Db. - Connect to the DB using the SQL ODBC with this user. Sadly if this doesn't run, It would look like a network problem.. Maybe yo