Errors
Michael Clarkson
quite serious if you are getting Cat_fix errors. It is vitally important
that you contact the supplyer that sold you the software for support. He
will require the Cat_fix.001 file that is genertated when you run a cat fix,
what he will be looking for is the error code for any severity 16
corruptions within the text of the log file.
Here, in the meantime is an explanation of the error messages you are
seeing on
the server and some suggestions.
One thing to be aware of is that the NT server should not be a Primary or
Backup Domain Controller as that could lead to
the sort of errors that you are seeing here. i.e. AWC, as it is not a
service and will take a low priority on the server.
In almost every instance when these errors have been reported,
the cause was either an 'overloaded' server (i.e. PDC) or a network
problem
(i.e. network card)
The following are extracts from Microsoft Technet.
Error : 17824, Severity: 10, State: 0
Unable to write to ListenOn connection '', loginname
Other relevant errors may follow, depending on the network
library used for the connection.In case of sockets based connections
(TCP/IP), errors
"10054 Connection reset by peer" may be logged.
These errors indicate that the connection between the client and
SQL Server was broken for some reason while SQL Server was writing data to
the
front end. Depending on the circumstances, a certain number of these
errors
may be normal, and eliminating them is not always necessary. If you do not
receive any end user complaints or experience general connection problems,
you
can ignore these errors.
Error 17824 "Unable to write to ListenOn connection" indicates
that problems have occurred while SQL Server attempted to write to a
client
connection and failed. These communication problems may be caused by
network
problems, or if the client computer has stopped responding or been
restarted.
This can happen if SQL Server attempts to write to a client
connection, and the write fails. This could be caused by the client
machine being
hung or shut down, or due to network problems. It is frequently seen if
client machines are rebooted.
Error 17824 does not always indicate a network problem. The
following are the most common situations under which the error 17824 is
generated,
along with the corresponding troubleshooting procedures.
- This error may occur if the users are restarting their client
computers if the application seems have stopped responding, so make sure
they
don't do that. It may be that the server is taking a longer time to
process a
long query. Once the client workstation is restarted, the connections are
broken
ungracefully. Later SQL Server tries to respond to the connection that
has been dropped, and
logs the message 17824.
- The network may be unstable; make sure it is stable. You can
check this by attempting to copy large files between the computer running
Windows NT Server and the client computer. If this test fails, then you
are
running into problems with the physical network.
Action
Inspect the Windows NT Event Viewer system and application logs
for information that may indicate whether or not the problem is related to
the
server network protocol, network card, or system configuration. Review the
SQL
Server specific entries in the application log or the SQL Server error log
for
relevant network-related errors that may occur in conjunction with this
error. If this review does not provide enough information to resolve the
problem, special network monitoring tools and a review of the client?s
configuration may be needed. If the problem persists, contact your primary
network support
provider for assistance.
10054 Connection reset by peer.
This can happen if a sockets client (which includes SPX) is
actively sending or receiving data to or from SQL Server, and the network
connection
is lost. This error is usually seen in conjunction with error 17824 when on
sockets-based connections. For example, an NT client using the NWLink SPX
transport could be selecting data from SQL Server, and if the network cable
is
unplugged from the SQL Server machine, you will see error 10054.
"Ventura Morcillo" <morci...@initec.es> wrote in message
news:ef00...@WebX.SaUCah8kaAW...
> Sometimes, we receive something similar:
> 98/09/21 11:05:40.88 server SQL Server's default sort order is:
> 98/09/21 11:05:40.88 server 'caseless_34' (ID = 49)
> 98/09/21 11:05:40.88 server on top of default character set:
> 98/09/21 11:05:40.88 server 'cp850' (ID = 2)
> 98/09/22 09:44:19.93 ods Error : 17824, Severity: 10, State: 0
> 98/09/22 09:44:19.93 ods Unable to write to ListenOn connection
'8000',
> loginname 'INITEC', hostname ''.
> 98/09/22 09:44:19.89 ods OS Error : 10054,
> 98/09/25 11:23:18.08 ods Error : 17832, Severity: 18, State: 0
> 98/09/25 11:23:18.08 ods Unable to read login packet(s).
> 98/09/25 11:26:42.07 ods Error : 17832, Severity: 18, State: 0
> 98/09/25 11:26:42.07 ods Unable to read login packet(s).
> 98/09/25 11:32:46.74 ods Error : 17824, Severity: 10, State: 0
> 98/09/25 11:32:46.74 ods Unable to write to ListenOn connection
'8000',
> loginname 'sa', hostname 'MORCILLO-V'.
> 98/09/25 11:32:46.74 ods OS Error : 10054,
> 98/09/25 12:36:58.13 ods Error : 17832, Severity: 18, State: 0
> 98/09/25 12:36:58.13 ods Unable to read login packet(s).
> 98/09/25 12:40:22.22 ods Error : 17832, Severity: 18, State: 0
> 98/09/25 12:40:22.22 ods Unable to read login packet(s).
>
> 17832 and 17824 errors are related, Microsoft says:
>
> Explanation:
> This error can occur when a client platform hangs or has been powered off,
> or when a network error has occurred. This error can appear in the SQL
> Server error log or the Windows NT Event Viewer application log if SQL
> Server attempts to write results to a client connection and the write
> operation fails.
>
> Action:
> Inspect the Windows NT Event Viewer system and application logs for
> information that may indicate whether or not the problem is related to the
> server network protocol, network card, or system configuration. Review the
> SQL Server-specific entries in the application log or the SQL Server error
> log for relevant network-related errors that may occur in conjunction with
> this error. If this review does not provide enough information to resolve
> the problem, special network monitoring tools and a review of the client's
> configuration may be needed.
> If the problem persists, contact your primary network support provider for
> assistance.
>
> But users are still able to login WorkCenter, so it seems to me that your
> problem is similar but not equal.
>
> 10054 error is encountered when a bulk copy of a row is too big to be
> completed. It sounds not very good, but I guess nothing wrong is happening
> with your database. The former error is the cause.
>
> I hope this helps you.
> --
>
> Ventura Morcillo - 34 (9)1 5871092
> Dpto. Tecnología
> mailto:morci...@initec.es
> http://www.initec.es
>
> "MrJones" <mrj...@teamicms.com> escribió en el mensaje
> news:ef00a...@WebX.SaUCah8kaAW...
> > We are receiving the following errors in the WC properties window on our
> WC
> > Server.
> > Does any one else get these types of errors?
> > Does anyone know what they mean?
> > WC server is a 200Mhz Dell with Windows NT 4.0 SP 6 128 MB Ram.
> >
> > 00/04/17 15:34:15.18 ods Error : 17824, Severity: 10, State: 0
> > 00/04/17 15:34:15.18 ods Unable to write to ListenOn connection
> '8000',
> > loginname 'ingersol', hostname ''.
> > 00/04/17 15:34:15.18 ods OS Error : 10054, Connection reset by peer
> > 00/04/17 15:34:15.23 ods Error : 17824, Severity: 10, State: 0
> > 00/04/17 15:34:15.23 ods Unable to write to ListenOn connection
> '8000',
> > loginname 'ingersol', hostname ''.
> > 00/04/17 15:34:15.23 ods OS Error : 10054, Connection reset by peer
> > 00/04/17 15:34:15.23 server Error : 1608, Severity: 21, State: 2
> > 00/04/17 15:34:15.23 server A network error was encountered while
> sending
> > results to the front end. Check the SQL Server errorlog for more
> > information.
> >
> > After we receive the errors Cat_Fix will find the following corruption:
> > DBCC CHECKALLOC: SYSTEM CORRUPTION DETECTED,
> > C:\SAROS\INGERSOL\UTIL\CAT_FIX.EXE COMPLETED WITH A DBI ERROR: 16477
> (405d)
> > AT LINE: 664
> >
> > Then we must reset the server because WC quits responding at the client
> end.
> > This has been happening since 1998 and we have been working around it by
> > resetting the server.
> > The problem is that it is occuring more often now. Used to be once every
> > other month but now it's at least once a week we must reset the server
> > because of these errors. The errors are always the exact same ones.
> >
> > We run Cat_Fix once a day and Cat_index after we reset the server.
> >
> > Thanks,
> > MrJ
> >
>