Microsoft odbc sql server driver ошибка связи

• Remove From My Forums

All replies

• We’re seeing the same thing as we’re supporting a company that runs an application that creates a new connection for each command.

  Their hardware setup is a Dell 1800 w/Dual 3GHz Xeons and raid array, connected to a Cisco 2948 catalyst switch for network.

  The database is running the 2005 version of msde… SQL Express i believe.

  A host of errors they get… at least a few times a day

  Error: 08S01 — Communication link failure

  Error: 01000 — ConnectionWrite (send())

• I have the same issue. Got any solution.

• I have the same issue at around 1400 connections to SQL.   Any resolution?

• We have the same errors.. «Communication link failure» often preceeded by the «ConnectionWrite(send())» error.  This is on a 3rd party application so we don’t know the internals of how it functions.  Suspect that it likewise creates a new connection for each command but not really sure.

  The application runs on multiple app servers and they connect to a dedicated database server.

  Database server is 64 bit Server 2003 with 64 bit SQL 2005, 4 dual core processors, and 16 GB RAM.

  We have looked at almost everything and cannot isolate the problem or find a solution.

  Any suggestions would be appreciated.

• I’ve got a customer with the same issue. They are the only customer I have running the queries over the WAN.

  I had one example where trying to connect to one SQLServer server I got the message. Trying to connect to another server, did not get the problem. Rebooting the client machine solved (and typically solves) this problem.

  If anyone has info on this, it would be greatly appreciated. Doesn’t look like this question’s getting much attention.

• I got a similar message. I’m working on a VM and it says OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: No process is on the other end of the pipe.
  ; 08S01.

  When I try to process an Analysis Services cube.

  Any ideas anyone?

• Same here, please respond if there is any available solution.

• I have an application that uses ADO to create recordsets on the fly and throw them away after reading data, using one connection object.

  If used on a local

  SQL Server 2005, the communication link failure occures when network connection broke down between two uses of recordsets. The temporary disrupted network connection (eg. WLAN) has nothing to do with the communication between application and server (local), and the connection is not broken at the time the error occures. This can be reproduced by temporary disconnecting any network connection.

  The property Connection.Connected is still true after network connetcion failed temporary. So my workaround is to catch up the error at Recordset.Open, reconnect if Error.SQLState is 08S01 (setting

  Connection.Connected to false and true), and try again.

• Martin, i know this is a very very old thread but we are seeing this same issue. Did VMWare ever help on the issue (you had said you had a case open with them)? Brent

• TruckinITGuy (Brent)…  Did you ever determine a cause and get a fix for this?  We are having the same problem on ESX.  I found another article that suggested changing the value of SynAttackProtect (below).  We probably have that set
  to 1 for better security, I am going to try to set that back to 0 and see if that helps.  But if you made headway, I would appreciate knowing how.  Jeff

  
  The following parameters can be used with this registry value:

  • 0 (default value): No SYN attack protection
  • 1: Set SynAttackProtect to 1 for better protection against SYN attacks. This parameter causes TCP to adjust the retransmission of SYN-ACKS. When you set SynAttackProtect to 1,
    connection responses time out more quickly if the system detects that a SYN attack is in progress. Windows uses the following values to determine whether an attack is in progress:
    • TcpMaxPortsExhausted
    • TCPMaxHalfOpen
    • TCPMaxHalfOpenRetried

• I know this thread is old.  Did anyone ever get this issue resolved?  I am experiencing the same issue with VM running on ESXi 3.5 and the system had been running fine since 2008. Nothing has changed in the system, but users are getting disconnected
  several times a day from our ERP system for two weeks now. SQL 2005 SP3 On Windows 2003 64 Bit.

  ---

  ra

  • Proposed as answer by

    Monday, October 28, 2013 5:48 PM

• We are also getting the out of memory error when processing an AS cube that had previously run fine.

    «OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Communication link failure; 08S01; Shared Memory Provider: No process is on the other end of the pipe.»

  The Windows System Event Viewer Log revealed a ‘Resource-Exhuastion-Detector’ Warning:

      «Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: sqlservr.exe (1280) consumed 13694660608 bytes, msmdsrv.exe (5464) consumed 10279247872 bytes, and Ssms.exe (4032)
  consumed 775794688 bytes.»

  We are expanded the PageFile on the VM and will see if that helps.  We are also rebooting the server and performing delayed monthly maintenance, so that may also contribute to the solution.

  The lack of memory has also caused the MSSQLSERVEROLAPService to crash and stop itself. 

      «The description for Event ID 22 from source MSSQLServerOLAPService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the
  component on the local computer.

     If the event originated on another computer, the display information had to be saved with the event.

     The following information was included with the event:

     Internal error: An unexpected exception occurred.

     the message resource is present but the message is not found in the string/message table»

  ———-

  UPDATE: Expanding the PageFile on the VM seemed to have resolved the problem.  The AS Cube processed successfully.

  • Proposed as answer by
    ColSanders
    Tuesday, October 29, 2013 10:55 PM
  • Edited by
    ColSanders
    Wednesday, October 30, 2013 3:54 AM

Answers

• Hi homeguards,

  «Communication link failure” means that an existing ODBC connection was closed, and we tried to use that connection. Usually an existing connection being dropped is either a failure of a client to sent packets to keep the connection open, or intermediate network hardware dropping a connection, or SQL Server having a problem.

  To determine who is dropping the connection, we needed simultaneous network captures on both the client and SQL Server, for the few moment before the issue, and during the issue.

  Generally, we can try these things to solve the issue:
  1.Disable TCP Chimney and other Scalable Network Features per http://support.microsoft.com/kb/951037/en-us
  2.Enable the SQL Server port in Firewall.
  3.Update the Network Interface Care driver.

  If there is anything unclear, pleaes feel free to ask.

  Thanks,
  Jin Chen

  ---

  Jin Chen — MSFT

  • Marked as answer by

    Monday, March 8, 2010 2:30 AM

• Remove From My Forums

All replies

• usually I’ve seen this issue due to network unavailability

  Check if you’ve any issues with your network connection, latency etc

  ---

  Please Mark This As Answer if it solved your issue
  Please Vote This As Helpful if it helps to solve your issue
  Visakh
  —————————-
  My Wiki User Page
  My MSDN Page
  My Personal Blog
  My Facebook Page

• • Marked as answer by

    Thursday, February 8, 2018 9:06 PM

  • Unmarked as answer by
    tygerl
    Monday, February 12, 2018 12:39 PM

• Xi,

  Windows Automatic Updates were disabled to start.  I did notice that the NIC1 adapter was being accessed as a secondary adapter when it is the one with the connection so I moved this up to #1.  Network connection is now working better.

  However, when leaving the application running on the client computer after a short amount of time we start getting the errors: Connection failure (-2147467259),  [DBNETLIB][ConnectionWrite
  (send()).]General network error. Check your network documentation. (-2147467259),  SharedDBLogOut: Connection failure (-2147467259).

• Remove From My Forums

All replies

• usually I’ve seen this issue due to network unavailability

  Check if you’ve any issues with your network connection, latency etc

  ---

  Please Mark This As Answer if it solved your issue
  Please Vote This As Helpful if it helps to solve your issue
  Visakh
  —————————-
  My Wiki User Page
  My MSDN Page
  My Personal Blog
  My Facebook Page

• • Marked as answer by

    Thursday, February 8, 2018 9:06 PM

  • Unmarked as answer by
    tygerl
    Monday, February 12, 2018 12:39 PM

• Xi,

  Windows Automatic Updates were disabled to start.  I did notice that the NIC1 adapter was being accessed as a secondary adapter when it is the one with the connection so I moved this up to #1.  Network connection is now working better.

  However, when leaving the application running on the client computer after a short amount of time we start getting the errors: Connection failure (-2147467259),  [DBNETLIB][ConnectionWrite
  (send()).]General network error. Check your network documentation. (-2147467259),  SharedDBLogOut: Connection failure (-2147467259).

I need your help on this guys!!!!

During the upload of the files to a database, this error occurs.
[Microsoft][ODBC SQL Server Driver]Communication link failure

Now here’s what I did so far based on the articles which I’ve been reading.
1. I restarted the servers that are involved.
2. I’ve added a new DNS connection to pattern to what they are using to connect to the database.

But all of these failed. I don’t know what to do because this is now critical and it’s been a week now.

Please help me…

asked Feb 16, 2011 at 7:19