|
Home > Archive > MS SQL Server ODBC > January 2006 > Read Failure General SQL Error
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 |
Read Failure General SQL Error
|
|
|
| I am using Delphi 5 Enterprise version and SQL Server 2000. So, I use the
odbc bridge. SQL Client connects through TCP/IP(not named pipes). My
application works alright, but sometimes, the clients get this Error Read
Failure General SQL Error [Microsoft][ODBC SQL Server Driver]Communication
Link Failure. The client may works fine again for hours and again this
problems repeats. Please let me know of any solution. What should I do ?
| |
| Arnie 2006-01-31, 11:23 am |
| "IGLC" < rightwayonline@hotma
ildot.com> wrote in message
news:OyrAX$lJGHA.1848@TK2MSFTNGP12.phx.gbl...
>I am using Delphi 5 Enterprise version and SQL Server 2000. So,
>I use the
> odbc bridge. SQL Client connects through TCP/IP(not named
> pipes). My
> application works alright, but sometimes, the clients get this
> Error Read
> Failure General SQL Error [Microsoft][ODBC SQL Server
> Driver]Communication
> Link Failure. The client may works fine again for hours and
> again this
> problems repeats. Please let me know of any solution. What
> should I do ?
I think the error message says it all. The connection was
dropped.
- Arnie
| |
|
| OK, but why it was't happen befor.
and how to fix it.
| |
|
| "IGLC" < rightwayonline@hotma
ildot.com> wrote in message
news:OGYGOaoJGHA.1424@TK2MSFTNGP12.phx.gbl...
> OK, but why it was't happen befor.
> and how to fix it.
>
It depends on the network to some extent. Connections should be
fairly solid on a LAN, server reboots aside. It would be more
likely to happen when using the internet and/or a VPN.
The error can be difficult to recover from. Certainly, the
SELECT (or whatever) should be in a try/catch block. You could
then catch the error, try a reconnect and retry the operation.
Not easy if you have a lot of DB I/O operations.
The only other thing I can think of is that SQL Server may have
an inactivity timeout. If this were the case, it might drop the
connection after some period of inactivity.
- Arnie
|
|
|
|
|