Home > Archive > MS SQL Server ODBC > June 2005 > ODBC connection frequently drops in routed network









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author ODBC connection frequently drops in routed network
Thomas Liss

2005-05-03, 7:23 am

Hello,

we are having serious problems with an application that uses an ODBC
connection (System DSN) to a SQL Server in another subnet. The network is
fine, all network tests reveal nothing of consequence. However, the problem
does not appear when SQL server and client are in the same subnet.

The ODBC connection from the client gets dropped at seemingly random
intervals and in the logs one can see the following:

{NIL, 10054, [01000][10054][Micro
soft][ODBC SQL Server
Driver][DBNETLIB]Con
nectionWrite (send()).}

{NIL, 59, [01000][59][Microsof
t][ODBC SQL Server
Driver][DBNETLIB]Con
nectionWrite (WrapperWrite()).}

{NIL, -1, [08S01][0][Microsoft
][ODBC SQL Server
Driver]Communication
link failure}

We honestly don't know what else to look for. Maybe anyone has an idea?



Thanks in advance,



Thomas Liss


Thomas Liss

2005-05-04, 7:23 am

Well, after configuring "Flow Control" on the network cards of the SQL
Server, the problems were gone.



"Thomas Liss" <liss@uipugmbh.com> wrote in message
news:upFsIo9TFHA.2664@TK2MSFTNGP15.phx.gbl...
> Hello,
>
> we are having serious problems with an application that uses an ODBC
> connection (System DSN) to a SQL Server in another subnet. The network is
> fine, all network tests reveal nothing of consequence. However, the
> problem does not appear when SQL server and client are in the same subnet.
>
> The ODBC connection from the client gets dropped at seemingly random
> intervals and in the logs one can see the following:
>
> {NIL, 10054, [01000][10054][Micro
soft][ODBC SQL Server
> Driver][DBNETLIB]Con
nectionWrite (send()).}
>
> {NIL, 59, [01000][59][Microsof
t][ODBC SQL Server
> Driver][DBNETLIB]Con
nectionWrite (WrapperWrite()).}
>
> {NIL, -1, [08S01][0][Microsoft
][ODBC SQL Server
> Driver]Communication
link failure}
>
> We honestly don't know what else to look for. Maybe anyone has an idea?
>
>
>
> Thanks in advance,
>
>
>
> Thomas Liss
>
>



Marko Erzen

2005-06-09, 3:23 am

Could you please explain what was the old setting and what is the new one?

Regards,
Marko Erzen

"Thomas Liss" <liss@uipugmbh.com> wrote in message
news:e2wez$JUFHA.2172@TK2MSFTNGP15.phx.gbl...
> Well, after configuring "Flow Control" on the network cards of the SQL
> Server, the problems were gone.
>
>
>
> "Thomas Liss" <liss@uipugmbh.com> wrote in message
> news:upFsIo9TFHA.2664@TK2MSFTNGP15.phx.gbl...
is[color=darkred]
subnet.[color=darkred]
>
>



Douglas Lane

2005-06-15, 8:23 pm


Thomas,

I just read your post and we are experiencing the same kind of error
here. The communication link failure is only occurring for clients
connecting from outside of the server's home subnet and the failure is
intermittent. Did you ever resolve your problems?


*** Sent via Developersdex http://www.droptable.com ***
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2009 droptable.com