INET/inet_error: accept errno = 10022 (log error)
Kristy Floyd
replaced this, but am still getting the 10022 error.
Microsoft says this is because the WSADuplicateSocket API returns
WSAEINVAL(10022) if you use it to duplicate a socket created using the
Microsoft provided QOS-capable TCP and UDP Winsock 2 service providers. It
says the resolution is to not use WSADuplicateSocket when you write a
GQOS-enabled application.
I'm not sure what I need to do to stop getting this error. I am still
having to restart my services every day at least once. Is there a setting I
need to change?
Kristy
Craig Stuntz
> I have found that log error 10054 could mean a bad NIC card. I have
> replaced this, but am still getting the 10022 error.
>
> Microsoft says this is because the WSADuplicateSocket API returns
> WSAEINVAL(10022) if you use it to duplicate a socket created using the
> Microsoft provided QOS-capable TCP and UDP Winsock 2 service providers.
Really? NET HELPMSG 10022 yields:
An invalid argument was supplied.
...and IB didn't use Winsock 2 until version 6.5. Prior to IB 6.5,
IB used Winsock 1.
> I'm not sure what I need to do to stop getting this error. I am still
> having to restart my services every day at least once. Is there a setting I
> need to change?
The first thing I'd try is to reinstall IB and/or Windows, since
that's pretty easy (IB, anyway). If this doesn't fix the problem by
itself, use a SQL monitor to try and correlate the error to a particular
activity with the DB.
HTH,
-Craig
--
Craig Stuntz (TeamB) · Vertex Systems Corp. · Columbus, OH
Delphi/InterBase WebLog: http://delphi.weblogs.com
InterBase PLANalyzer (Free IB optimization tool):
http://delphi.weblogs.com/IBPLANalyzer
Achim Kaiser
Error 10054 means
WSAECONNRESET
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.)
It could be caused by a bad NIC-card,
but could be also anything else,
starting with bad line, user reseting programms etc. etc
Error 10022 means
WSAEINVAL
Invalid argument.
Some invalid argument was supplied (for example, specifying an invalid level
to the setsockopt function). In some instances, it also refers to the
current state of the socket - for instance, calling accept on a socket that
is not listening.
It could be caused by a driver-problem
or by a programminig error.
Both are Winsock-Network errors and could be caused by *ANY* programm
running on your client.
(e.g. bad printer configuration or drivers etc. etc.)
If your connection to the server is cut off,
you will allways find a error-message in your logfile,
because your server had lost the connection to the client
but it doesn´t mean there was a Interbase Error
it means there was a "NETWORK-Error" witch is sometimes difficult to find
*sorry for the bad news*.
As Crain said get the latest driver-updates for Windows and your NIC-Cards
and the latest printer drivers.
( I had some printer trouble, caused by a driver problem at the server until
a seperate printer-server was setup in the network, now the dataserver
doesn´t die,
when my printerserver had a problem and kills the machine)
HTH
Achim