RE: Error 10054: [DBNETLIB]ConnectionRead/ConnectionWrite
From: Kevin McDonnell [MSFT] (kevmc_at_online.microsoft.com)
Date: 09/10/04
- Previous message: Kevin McDonnell [MSFT]: "RE: Must specify protocol/Named Instance"
- In reply to: TN: "RE: Error 10054: [DBNETLIB]ConnectionRead/ConnectionWrite"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 10 Sep 2004 17:26:50 GMT
Right. You trace indicates that we're unable to write data back to the
server.
pfwin 55c-558 ENTER SQLExecDirect
HSTMT 066FA478
UCHAR * 0x0DADA5F8 [ -3] "DELETE FROM
PTWinTran
s WHERE ((fileid = '06006537ECC') AND ((rectype = 2) OR (rectype = 3)))\ 0"
SDWORD -3
pfwin 55c-558 EXIT SQLExecDirect with return code -1 (SQL_ERROR)
HSTMT 066FA478
UCHAR * 0x0DADA5F8 [ -3] "DELETE FROM
PTWinTran
s WHERE ((fileid = '06006537ECC') AND ((rectype = 2) OR (rectype = 3)))\ 0"
SDWORD -3
DIAG [01000] [Microsoft][ODBC SQL Server Driver][TCP/IP
Sockets]
ConnectionWrite (send()). (10054)
This error 10054, means that the client connection reset the connection
more than likely. A network trace on the client side would confirm this.
If you were to execute the same statement from ISQL.exe would the statement
complete?
(ISQL.exe) uses dblibrary and doesn't go thru ODBC.
Since the problem only happens remotely, I would doublecheck the routers
and switches in between.
Check all the duplex settings.
This can cause intermittant failures.
See Cisco's document:
http://www.cisco.com/en/US/tech/tk389/tk214/technologies_tech_note09186a0080
094781.shtml
Configuring and Troubleshooting Ethernet 10/100/1000Mb Half/Full Duplex
Auto-Negotiation
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
- Previous message: Kevin McDonnell [MSFT]: "RE: Must specify protocol/Named Instance"
- In reply to: TN: "RE: Error 10054: [DBNETLIB]ConnectionRead/ConnectionWrite"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|