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

Chapter 19 371
Logging Location Codes
Control Process Logging Location Codes
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 an SR,” of this manual.
MESSAGE: Bad status
657 CLAS0002 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 an
SR,” of this manual.
MESSAGE: INTERNAL ERROR; Internal resource error
658 CLAS0002 CAUSE: While attempting to start all network specific protocols,
required for a given network, such as IP, because a :NETCONTROL
command was issued, NETCP encountered an error, either from a
protocol’s module configurator, or while trying to rendezvous a protocol
to the link driver. (PARM = 32-bit status returned by the call to a
module configurator, or from cp_rendezvous_protocol). May be
preceded by another error from another module, logging the reason for
the original failure.
ACTION: The general protocols were started, but the specified network
did not start, and NETCP attempted to stop the partially started
network and any network specific protocols which did start. Retry the
operation. If the problem still occurs, stop and restart Transport. If the
problem still persists, see Appendix A, “Submitting an SR,” of this
manual.
MESSAGE: INTERNAL ERROR; Module Deconfig Failed
659 CLAS0002 CAUSE: After an error occurred while NETCP was attempting to start
network specific protocols for a given network, NETCP attempted to
clean up by stopping any of those protocols which did start, but then
encountered another error when calling a protocol module
deconfigurator (PARM = 32-bit status returned by the call to a module
deconfigurator, or from cp_rendezvous_protocol). Should always be
preceded by other errors, logging the reasons for the original failures.