Ers: Connection Failed, Connection Read, Connection Write 
Author Message
 Ers: Connection Failed, Connection Read, Connection Write
I am suddenly getting lots of these errors from people in our remote office
connecting through a dedicated T-1 circuit(s) to our server.

They use ADO, the connection string explicitly declares TCP/IP as the
connection type (NTL=TCPIP).

Everything else about our network is working fine.

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send())

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (rcvd))

[Microsoft][ODBC SQL Server Driver]Communication link failure



Sat, 01 May 2004 04:47:17 GMT
 Ers: Connection Failed, Connection Read, Connection Write



Quote:
> I am suddenly getting lots of these errors from people in our remote
> office connecting through a dedicated T-1 circuit(s) to our server.

> They use ADO, the connection string explicitly declares TCP/IP as the
> connection type (NTL=TCPIP).

> Everything else about our network is working fine.

> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite
> (send())

> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead
> (rcvd))

> [Microsoft][ODBC SQL Server Driver]Communication link failure

Do any remote users connect?  Did someone suddenly throw up a new firewall
or somehow change the firewall on your network?

--
Mike Harms
SQL Server MVP



Sat, 01 May 2004 06:48:52 GMT
 Ers: Connection Failed, Connection Read, Connection Write
They can connect fine, and just go along great and then suddenly, they get
one of the errors.  I'm trying to find if there is any thing like a time out
setting for the connection or something, but when I ask them, they say they
are continually working.


Quote:


> > I am suddenly getting lots of these errors from people in our remote
> > office connecting through a dedicated T-1 circuit(s) to our server.

> > They use ADO, the connection string explicitly declares TCP/IP as the
> > connection type (NTL=TCPIP).

> > Everything else about our network is working fine.

> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite
> > (send())

> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead
> > (rcvd))

> > [Microsoft][ODBC SQL Server Driver]Communication link failure

> Do any remote users connect?  Did someone suddenly throw up a new firewall
> or somehow change the firewall on your network?

> --
> Mike Harms
> SQL Server MVP



Sat, 01 May 2004 07:00:35 GMT
 Ers: Connection Failed, Connection Read, Connection Write
Keith...
    Have not gotten an answer from any of then, including .connect...

:-(

-js



Quote:
> This is being cross-posted to multiple groups, including .Connect which is

a better place to get an answer.
Quote:

> =================================================
> *  This posting is provided "AS IS" with no warranties, and confers no
rights.
> *  Please do not send email directly to this alias.Respond to newsgroup

> --------------------

> |>Newsgroups:

microsoft.public.sqlserver,microsoft.public.sqlserver.connect,microsoft.publ
ic.sqlserver.misc,microsoft.public.sqlserver.od
bc,microsoft.public.sqlserver.programming,microsoft.public.sqlserver.server
Quote:
> |>Subject: Ers: Connection Failed, Connection Read, Connection Write
> |>Date: Mon, 12 Nov 2001 20:47:17 GMT

> |>
> |>I am suddenly getting lots of these errors from people in our remote
office
> |>connecting through a dedicated T-1 circuit(s) to our server.
> |>
> |>They use ADO, the connection string explicitly declares TCP/IP as the
> |>connection type (NTL=TCPIP).
> |>
> |>Everything else about our network is working fine.
> |>
> |>[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite
(send())
> |>
> |>[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead
(rcvd))
> |>
> |>[Microsoft][ODBC SQL Server Driver]Communication link failure
> |>
> |>
> |>
> |>



Sat, 01 May 2004 22:32:41 GMT
 Ers: Connection Failed, Connection Read, Connection Write
Someone should get around to it soon but this is a connectivity issue.
Here are some basic things to do in the meantime:

   - Check for any errors in the SQL errorlog at the times of the failures. If there are access violations, then make sure
     you have the latest service pack.
   - Check if you can use any SQL Server client utility to connect to the SQL Server from those clients with the problems.
     If this is successful, you will need to use SQL Profiler to trace what was the last query your app was executing?
   - Is the server PING'able from the client using the servername? If no, this is a network problem.
   - Are the clients having the problem on a different subnet? If so, then more network problems
   - Is SQL Server responding at all to any connection, including a local connection on the server itself? If responding, then
network or possible SQL errors in the errorlog.

-Keith

=================================================
*  This posting is provided "AS IS" with no warranties, and confers no rights.
*  Please do not send email directly to this alias.Respond to newsgroup

--------------------

|>Newsgroups: microsoft.public.sqlserver.programming

|>Subject: Re: Ers: Connection Failed, Connection Read, Connection Write

|>
|>Keith...
|>    Have not gotten an answer from any of then, including .connect...
|>
|>
|>:-(
|>
|>-js
|>


|>> This is being cross-posted to multiple groups, including .Connect which is
|>a better place to get an answer.
|>>
|>> =================================================
|>> *  This posting is provided "AS IS" with no warranties, and confers no
|>rights.
|>> *  Please do not send email directly to this alias.Respond to newsgroup
|>>
|>> --------------------

|>> |>Newsgroups:
|>>
|>microsoft.public.sqlserver,microsoft.public.sqlserver.connect,microsoft.publ
|>ic.sqlserver.misc,microsoft.public.sqlserver.od
|>>
|>bc,microsoft.public.sqlserver.programming,microsoft.public.sqlserver.server
|>> |>Subject: Ers: Connection Failed, Connection Read, Connection Write
|>> |>Date: Mon, 12 Nov 2001 20:47:17 GMT
|>>
|>> |>
|>> |>I am suddenly getting lots of these errors from people in our remote
|>office
|>> |>connecting through a dedicated T-1 circuit(s) to our server.
|>> |>
|>> |>They use ADO, the connection string explicitly declares TCP/IP as the
|>> |>connection type (NTL=TCPIP).
|>> |>
|>> |>Everything else about our network is working fine.
|>> |>
|>> |>[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite
|>(send())
|>> |>
|>> |>[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead
|>(rcvd))
|>> |>
|>> |>[Microsoft][ODBC SQL Server Driver]Communication link failure
|>> |>
|>> |>
|>> |>
|>> |>
|>>
|>>
|>
|>
|>
|>



Sun, 02 May 2004 03:59:10 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. Connection Fail after installation - dbnmpntw write() connection fail

2. Connection Fail after installation - dbnmpntw write() connection fail

3. Help - Connection Error - [TCP/IP Sockets]Connection Read[recv(0)]

4. Dynaset with Bookmarks to SQL Server connection makes a CRecordset connection read-only

5. TCP/IP Connection to SQL fails/Connection Pooling

6. ADO connection passed to a DLL fails to maintain valid connection

7. Hanging connections from a failed update or insert (connection pooling)

8. SqlServer client connections hang, new connections fail

9. Connection fails due to: invalid connection string attribute (01S00)

10. error CONNECTION FAILED ( CONNECTION OPEN (CREATEDFILE())

11. ODBC Connection - read/write access

12. Error reading/writing to connection


 
Powered by phpBB® Forum Software