Communications Error Messages

Transport Messages:

Code Description

---- ----------------------------------------------------------------

151 Bad socket descriptor

152 Address already in use

153 Invalid operation

154 User address parameter fault

155 Net/host unreachable

156 Message overflow error

157 Destination socket does not exist

158 Address family does not exist

159 Socket type does not exist

160 Protocol does not exist

161 No more sockets available

162 No buffer space available

163 Timeout event

164 Operation not supported

165 Resource not available

166 Internal communication service fail

167 Controller reset fail

Often observed communication errors:

COM155

Net/host unreachable.

> Net/host (server or PC) is unreachable.

> A routing table entry was found neither for:

- The net_ID and subnet_ID in the neighbors table, nor

- The net_ID in the all known networks table.

> A routing table entry was found, but the metric was set to 0xFFFF.

COM157

Destination socket does not exist.

> Message was successfully routed to the destination, but the transport

layer determined the port number was not assigned to a process.

- Process may not be running currently, e.g. it was stopped.

- Or process may have closed the socket, but is still running.

> A routing table entry was found and a packet was sent but an ACK was

not returned even after the retry counter limit was reached.

COM163

Time-out event.

> Message was successfully routed to destination, transport layer passed

to process, and transport layer returned ACK, but process did not

return data response message in time.

> When wait time (RPC exec time + total path metric) is exceeded a time-out

error occurs, source transport layer informs process.

> A network disruption or network congestion may have occurred.

> The destination process has subsequently failed, is in a loop, or

simply relatively too slow at generating response message.

> Source process commonly closes socket, COM157 may then occur.