NetIPC 3000/XL Programmer's Reference Manual (5958-8600)

192 AppendixC
Error Messages
NetIPC Errors
35 MESSAGE: ATTEMPT TO EXCEED LIMIT OF NAMES PER SOCKET.
CAUSE: A socket can have only four names; the caller attempted to give
it a fifth.
ACTION: Use no more than four names.
36 MESSAGE: TABLE OF NAMES IS FULL.
CAUSE: Socket registry or give table is full.
ACTION: Shut down unused sockets, call IPCNAMERASE on any sockets
that no longer need to be looked up, or get given sockets. See
“Submitting an SR” at the end of this appendix.
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
“Submitting an SR” at the end of this appendix.