Could you please shed some light on the following?
Certain SQL update statements cause the error 10054. (Interbase 7.1) It
doesn't matter whether they are executed from an application or from e.g.
ibconsole.
This is very annoying as all workstations are then disconnected from the
server and everyone's transactions are disrupted.
Can anyone help?
Sando
It looks like certain SQL statements break down the Interbase server.
What's in error log?
Possible cause might be a corrupted database. Can you execute those
statements against a newly created database?
Kris
> Possible cause might be a corrupted database.
Or a UDF.
-Craig
--
Craig Stuntz [TeamB] . Vertex Systems Corp. . Columbus, OH
Delphi/InterBase Weblog : http://delphi.weblogs.com
IB 6 versions prior to 6.0.1.6 are pre-release and may corrupt
your DBs! Open Editon users, get 6.0.1.6 from http://mers.com
The database is a fresh one (we create a new one regularly as we are
testing) and we don't use UDF's.
Have you got any other ideas?
We dare not install our app at the customer's system because of this...
> Have you got any other ideas?
In that case it's either a particular piece of SQL or a network
problem. If possible, install IB 7.1 which will tell you in the log
file which client's transmission caused the error.
-Craig
--
Craig Stuntz [TeamB] . Vertex Systems Corp. . Columbus, OH
Delphi/InterBase Weblog : http://delphi.weblogs.com
Everything You Need to Know About InterBase Character Sets:
http://delphi.weblogs.com/stories/storyReader$306
Very frequent (but do not have a specify time or module, mean can happen any
time in any module) the 'Unable to complete network request to host xxxxx.
Error writing data to the connection. Unknown Win32 error 10054' will pop
up. By then, all the trasaction will be lost in all other pc.
interbase.log give me this:
SERVER-1 (Client) Mon Aug 11 06:57:03 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Mon Aug 11 07:19:45 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Server) Mon Aug 11 15:36:51 2003
INET/inet_error: read errno = 10054
SERVER-1 (Server) Tue Aug 12 15:38:56 2003
INET/inet_error: read errno = 10054
SERVER-1 (Client) Tue Aug 12 15:54:05 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Tue Aug 12 16:08:39 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Wed Aug 13 06:44:00 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Wed Aug 13 07:38:10 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Server) Wed Aug 13 10:23:06 2003
INET/inet_error: read errno = 10054
SERVER-1 (Client) Wed Aug 13 11:18:36 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Wed Aug 13 12:07:32 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Wed Aug 13 13:08:10 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Server) Wed Aug 13 13:43:38 2003
INET/inet_error: read errno = 10054
SERVER-1 (Client) Wed Aug 13 23:26:04 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Thu Aug 14 07:00:20 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Thu Aug 14 07:03:04 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Thu Aug 14 07:38:52 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Server) Thu Aug 14 16:07:37 2003
INET/inet_error: read errno = 10054
SERVER-1 (Client) Fri Aug 15 06:52:11 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Fri Aug 15 16:30:10 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Fri Aug 15 16:54:44 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Sat Aug 16 07:11:20 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Sat Aug 16 12:57:56 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Sat Aug 16 13:33:42 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Mon Aug 18 06:40:50 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Mon Aug 18 10:08:46 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Server) Mon Aug 18 13:16:19 2003
INET/inet_error: read errno = 10054
SERVER-1 (Server) Mon Aug 18 15:28:23 2003
INET/inet_error: read errno = 10054
SERVER-1 (Server) Mon Aug 18 15:28:50 2003
INET/inet_error: read errno = 10054
SERVER-1 (Client) Mon Aug 18 16:40:25 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Client) Tue Aug 19 06:42:29 2003
Guardian starting: C:\Program Files\Borland\InterBase\bin\ibserver.exe
SERVER-1 (Server) Tue Aug 19 09:00:33 2003
INET/inet_error: read errno = 10054
SERVER-1 (Server) Tue Aug 19 09:16:06 2003
INET/inet_error: send errno = 10054
SERVER-1 (Server) Tue Aug 19 09:16:06 2003
INET/inet_error: read errno = 10054
SERVER-1 (Server) Tue Aug 19 16:19:12 2003
INET/inet_error: read errno = 10054
Please Help
Thank you
> Very frequent (but do not have a specify time or module, mean can
> happen any time in any module) the 'Unable to complete network
> request to host xxxxx. Error writing data to the connection. Unknown
> Win32 error 10054' will pop up. By then, all the trasaction will be
> lost in all other pc.
The server has crashed, probably due to one of the following:
o A specific piece of SQL.
o A buggy UDF.
o Network problems.
First step to diagnosing the problem: If you are using *any* UDFs in
your DB at all, replace them (temporarily) with UDFs from the standard
library. Does that make the problem go away?
If not, use SQL monitoring to see if you can connect the crashes with
a secific piece of SQL.
If that doesn't help, look for network problems. This is much easier
with IB 7.1, as 7.1 gives you the client name which experienced the
problem in the log file. You'll then have to replace network hardware
(NICs, cables, routers, etc.) until the problem goes away.
-Craig
--
Craig Stuntz [TeamB] . Vertex Systems Corp. . Columbus, OH
Delphi/InterBase Weblog : http://delphi.weblogs.com
InterBase in Multi-tier World -- Use multiple RDMs, IB features in
your appserver: http://delphi.weblogs.com/stories/storyReader$195