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

122 Chapter12
NETXPORTERR Error Messages
ACTION: Consult the NS 3000/iX Operations and Maintenance
Reference Manual for the correct syntax for the NETCONTROL command.
Once the syntax has been corrected, retry the command.
4060 MESSAGE: THIS UPDATE IS NOT ALLOWABLE FOR THIS ENTITY.
CAUSE: The entity associated with the NETCONTROL UPDATE command
may not be updated.
ACTION: Consult the NS 3000/iX Operations and Maintenance
Reference Manual for the correct syntax for the NETCONTROL command.
Once the syntax has been corrected, retry the command.
4061 MESSAGE: CONFIGURATION FILE NOT VALID.
CAUSE: Validation errors occurred on a NETCONTROL START or UPDATE
commands.
ACTION: Correct the invalid parameters in your configuration file and
try again.
4062 MESSAGE: UNABLE TO LOCK CONFIGURATION FILE. (NMERR=
error number).
CAUSE: Unable to lock the configuration file for execution of a
NETCONTROL START or UPDATE.
ACTION: Wait and try again; if problem persists, see Appendix A ,
“Submitting a CR,” of this manual.
4063 MESSAGE: PROTOCOL START FAILED.
CAUSE: During a NETCONTROL START one or more of the NI specific
protocols failed to start.
ACTION: Stop the network. Check the configuration of the effected
protocols to be sure that they are correct. Then restart the network. If
the error persists, then see Appendix A , “Submitting a CR,” of this
manual.
4064 MESSAGE: GENERAL PROTOCOL STARTUP FAILED.
CAUSE: During a NETCONTROL START one or more of the general
protocols or common modules failed to start. This prevented startup of
any NI-specific protocols. Any further attempts to start networks will
also fail, unless networking is first stopped.
ACTION: Do a netcontrol stop. Check the configuration of the TCP and
IP modules to be sure that they are correct. Then try restarting the
network. If the error persists, see Appendix A , “Submitting a CR,” of
this manual.
4100 MESSAGE: VERSION ERROR: INTERNAL ERROR (NMERR= error
number).
CAUSE: An internal error occurred while the network transport was
checking its module versions.