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

Chapter 5 65
NetIPC (SOCKERRS) Error Messages
ACTION: Shut down unused sockets, call IPCNAMERASE on any sockets
that no longer need to be looked up, or get given sockets. See Appendix
A , “Submitting a CR,” of this manual.
37 MESSAGE: NAME NOT FOUND.
CAUSE: Name was not previously specified in an IPCNAME or IPCGIVE
call; IPCNAMERASE or IPCGET was previously issued with the name; or
socket no longer exists.
ACTION: Check names specified, make sure names were properly
agreed on, determine if a timing problem exists.
38 MESSAGE: USER DOES NOT OWN THE SOCKET.
CAUSE: Attempted to erase a name of a socket you do not own.
ACTION: Have the owner of the socket call IPCNAMERASE.
39 MESSAGE: INVALID NODE NAME SYNTAX.
CAUSE: Syntax of the node name is invalid.
ACTION: Check the node name being supplied.
40 MESSAGE: UNKNOWN NODE.
CAUSE: Unable to resolve the specified node name as an NS node name.
ACTION: Check the node name to see if it is correct. The node name may
be valid but the specified node’s transport may not be active.
41 MESSAGE: ATTEMPT TO EXCEED PROCESS LIMIT OF DESTINATION
DESCRIPTORS.
CAUSE: User has already reached the limit of 261 destination
descriptors per process.
ACTION: Call IPCSHUTDOWN on any unneeded destination descriptors.
43 MESSAGE: UNABLE TO CONTACT THE REMOTE REGISTRY SERVER.
CAUSE: Send to remote socket registry process failed. This is often
caused by the fact that the PXP protocol module is not active on the
local node.
ACTION: Contact your operator. If unable to resolve the problem, see
Appendix A , “Submitting a CR,” of this manual.
44 MESSAGE: NO RESPONSE FROM REMOTE REGISTRY SERVER.
CAUSE: No reply was received from the remote registry process. This is
often due to the remote node not having initialized its transport.
ACTION: Contact your operator. If unable to resolve the problem, see
Appendix A , “Submitting a CR,” of this manual.