NS3000/iX Error Messages Reference Manual (36923-90043)

Chapter 21 521
Logging Location Codes
Control Process Logging Location Codes
655 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: While attempting to start all the general protocols because a
:NETCONTROL command was starting a new instance of Transport,
NETCP successfully started some modules, then encountered an error
trying to start the ICMP (PING) Server module (PARM = 32-bit escape
code returned by the call to pxp_module_config). Always preceded by
another error from another entity (having a different Entity number,
such as 151–160), logging the reason for the original failure.
ACTION: This error in itself was not fatal, and general protocol startup
continued. However, the PING service will not be available, and pings
from other nodes will go unanswered. To clear the problem, stop then
restart the network. If this problem persists, record the previous error
and this error, then see Appendix A , “Submitting a CR,” of this manual.
656 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: While attempting to start all the general protocols because a
:NETCONTROL command was starting a new instance of Transport,
NETCP successfully started some modules, then encountered an error
trying to start the Net Timers module (PARM = 32-bit status returned
by the call to nettmr_module_config). Always preceded by another
error from Net Timers, logging the reason for the original failure.
ACTION: TCP and ARP will not work without timers. Some versions of
Transport will erroneously continue the startup after this error. Record
the previous error and this error. Stop the network. Then try restarting
the network. If the problem still occurs, then depending on the error, it
is possible too much frozen memory is being used by the system, but
this can change with time. Use GLANCEXL or a similar utility to check
memory usage by the system. If memory is not the cause and the
problem persists even if retried after a suitable waiting period, see
Appendix A , “Submitting a CR,” of this manual.
657 CLAS0002 MESSAGE: Bad status
CAUSE: While attempting to start all the general protocols because a
:NETCONTROL command was starting a new instance of Transport,
NETCP successfully started some modules, then encountered an error
trying to create the Socket Registry (PARM = 16-bit result code
returned by the call to sock_registry_create). May be preceded by
another error from NETIPC, logging the reason for the original failure.
ACTION: Newer versions of Transport treat this as a fatal error, and
Transport startup will fail. For older versions of Transport this error
was not fatal, and startup will continue, but NETIPC and Sockets will
not work correctly. It is possible the Socket Registry encountered an
unreported error during its last shutdown. Try stopping and restarting
transport. If the error still happens, see Appendix A , “Submitting a
CR,” of this manual.