This error can be an indication of network problems.
But even in networks without (known) problems this
error occurs.

This can be due to client applications hanging up or
crashing.

You can easily reproduce it: open your client app,
kill the process with the NT task manager and watch
your server log: you will find an INET_ERROR 10054
exactly matching the time of your 'kill' command.

Our DB is in production since Dec 2000 and I have
5-10 errors a day with about 30 users (~10 connected
concurrently). Fortunately, there are no DB validation
errors.

So I can live with it.

How to prevent these errors?
Dunno, the first thing I will try is to improve my apps
so that they are bulletproof and do not crash.

Then I will see if these errors still occur.


HTH,

Christian

> -----Original Message-----
> From: Brian Dunstan [mailto:bdunstan@...]
> Sent: Thursday, March 01, 2001 7:38 AM
> To: 'ib-support@yahoogroups.com'
> Subject: [ib-support] Interbase.log errors
>
>
>
> MHS_SRV01 (Server) Thu Mar 01 10:38:31 2001
> INET/inet_error: read errno = 10054
> The times seem to correspond to when my user had problems,
> which makes me
> wonder what the error means.
>
> Windows SDK says:
> WSAECONNRESET
> (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.)
>
> But I am still left wondering who that might relate to my application.
>