10054 error

[Sean Bradley]

Hi,

I'm regularly getting the Interbase error 10054 returned by my Delphi4
application indicating that the application has lost it's connection to the
server.

This can happen to an individual client or all of the clients at once (The
IB server does not crash).

Q&A's on the web site suggest that it could be caused by network conditions,
however I can't find any evidence that the Network or Server is particularly
loaded at the time of the problems.

I'm using IB5.1 on a NT4 server.

Can anyone suggest what else could be causing the problem?

Thanks for any help,

Sean

[Ded]

Sean Bradley wrote:

Hi, Sean. I quote Ann Harrison:

10054
Connection reset by peer.
A existing connection was forcibly closed by the remote host. This normally
results if the peer application on the remote host is suddenly stopped, the
host is rebooted, or the remote host used a "hard close" (see setsockopt
for more information on the SO_LINGER option on the remote socket.) This
error may also result if a connection was broken due to "keep-alive"
activity detecting a failure while one or more operations are in progress.
Operations that were in progress fail with WSAENETRESET. Subsequent
operations fail with WSAECONNRESET.

Best regards.

[Dan Jensen]

I'm having a similar problem. Haven't solved it yet but this might help:

All connections lost at once with error 10054 - by Borland Developer Support
Staff

Abstract:Some sort of network error occured

Problem:
All connections lost at once with error 10054 in interbase.log. It can
happen with both Service pack 2 & 3 for NT 4.0. InterBase Server is
still running on the server.

Solution:
Error 10054 is a winsock error for connection reset. You can find the
list of winsock errors in the winsock.h file.

Since the InterBase Server is up and running at the time of the problem,
it's an indication that it's not an InterBase issue but rather a network
issue. Check the following:

* At the time of the problem, what's the traffic load? Check for
traffic loads that can flood the network. Is there anything scheduled
to flood the network at certain time?

* Check for network hardware problems such as bad switch, router,
hub, etc.

* Another possible scenario involves having more than one protocol
bound to the same network card. In one case a customer had TCP/IP,
IPX/SPX, and RIP for IPX bound to the same ethernet card. When he
unbound IPX/SPX and RIP for IPX from the card, the errors disappeared.

[Sean Bradley]

I think I can rule out the 3 networking problems.

Are you using SQL Links to connect to the server. If so what version?

Sean

"Dan Jensen" <jen...@inel.gov> wrote in message
news:3B1F9FDA...@inel.gov...

[Stan Walker]

We use to get this error a lot until we went to a dedicated server for
Interbase. We have an application that is used concurrently by about 20
users. Sometimes a user would just reboot their computer without getting out
of the application first. That would cause a 10054 error. They would reboot
because the application was going too slow for them. With the new, faster
server the user has less of a reason to reboot, but we still have about 10 a
day. Probably some users are still rebooting or there is another reason that
we haven't found.

[Dan Jensen]

Yes I am and it's the one that came with Delphi 5.0 enterprise. I believe
it's considered ver 5.0 but I'm not sure. However the app
was compiled with Delphi 4.0 (customer doesn't want to upgrade the
3rd party components that are only good for Delphi 4.0).

Got any new ideas on what's causing the problem?