Rockwell Automation Publication ENET-AT002E-EN-P - January 2023 39
Chapter 4 Troubleshoot Socket Applications
16#0008
A 1756-ENxT or 1756-ENxTR module that is used for socket messages is in a remote chassis that is connected to the controller
over the ControlNet® network or is using an older EtherNet/IP module that supports only 478-byte messages.
For more information, see the Knowledgebase Article Open Sockets: Message Read/Write error 16#0008 if "Large Connection"
option is enabled.
16#0009
Invalid socket descriptor. To resolve this error, do the following:
• Make sure that a valid socket instance exists.
• Make sure that the message source data format and source values are correct.
• For Create messages, make sure that Type and Family is set correctly.
• For UDP Read/Write messages, make sure that Source tag member Family is set to 2.
16#000b
or
16#000c
The Open (Connect) message instruction and Accept message were executed on the same socket.
For more information, see the Knowledgebase Article Open Sockets Error codes 16#000b, 16#000c
.
16#000d Invalid data in Source UDT.
16#0011
Failed attempt to read more than 484 bytes with a CompactLogix 5370 controller. SocketRead messages are limited to
484 bytes with CompactLogix 5370 controllers. This value is specified in the MessageSourceBuffLen tag.
16#0013
or
16#0015
The ‘Write’ message instruction Source length must be exactly equal to the buffer length+16.
For more information, see the Knowledgebase Article Open Sockets Error code 16#0013 and 16#0015
.
16#0020
The ‘Write’ message instruction Source length is less than 17 bytes. Length must be exactly equal to the buffer length+16.
For Connect messages, make sure that the Destination String address includes ‘?port=xxxx’ similar to 192.168.1.34?port=9100.
For more information, see the Knowledgebase Article 1756-EN2T, 1756-EWEB sockets error 16#0020
.
16#00ff
16#0000_0016
or
16#0000_0033
Open Sockets (TCP Client) is unable to connect to a third-party device (Slave). The device reports WIN=0 and the 1756-EN2T
module immediately closes the connection. For more information, see the Knowledgebase Article Open Sockets: Open
connection fails with error 16#0000_0046,16#0000_0016 or 16#0000_0033.
16#00ff 16#0000_0030 The address is already in use. This error can occur when multiple Socket Create requests are issued to the same port address.
16#00ff 16#0000_0036
A connection was forced closed by a peer. This error can occur when a remote device closes a connection with a Logix
module without notifying the module.
To resolve this error, delete the socket and then reconnect to the remote device.
16#00ff 16#0000_0039 In Server mode, instance number from Accept Message was not copied to Read/Write messages.
16#00ff 16#0000_003d
A connection refused by a peer. Possibly peer is out of connections if Logix module closes them without Linger Attribute set.
For more information, see the Knowledgebase Article Logix Open Sockets Linger Control
.
16#00ff 16#0000_0041
A socket operation could not find a route to the remote host. This error typically occurs in these scenarios:
• A remote IP address that is specified in the MSG instruction is not on the same subnet as the Logix module.
and
The IP address of the gateway or router is not specified in the Logix module properties.
• UDP multicasts messages to an unpingable IP address require you to specify a gateway address in the Logix module
properties even if a gateway address does not exist or is not required.
For more information, see the Knowledgebase Article 1756-EWEB socket errors 16#0041 and 16#0043
.
16#00ff 16#0000_0043
The remote device or gateway is not responding.
This error can occur if a UDP multicast message is sent to a gateway address that is not specified in the Logix module
properties.
For more information, see the Knowledgebase Article 1756-EWEB socket errors 16#0041 and 16#0043
.
16#00ff 16#0000_0046
The socket operation timed out. Known reasons include the following:
• Connect Service message:
– Server IP exists, but port does not.
– Server IP and port exist, but does not accept connections on this port.
– Service timeout value in UDT set to 0 or low value.
The peer device reports WIN=0 and the 1756-EN2T module immediately closes the connection. For more information, see the
Knowledgebase Article Open Sockets: Open connection fails with error 16#0000_0046,16#0000_0016 or 16#0000_0033.
• Read/Write Service message:
– Read and write executed simultaneously.
For more information, see the Knowledgebase Article Open Sockets message Error 16#00FF extended 16#0000_0046
.
• UDP Read message only:
– UDP Receive buffer is empty with no new incoming data.
16#00ff 16#0009_0315 Invalid path string manually or programmatically entered to the MSG.Path string.
16#00d0 16#0000_0001 CA certificate file has a loading error.
16#00d0 16#0000_0002 Trusted peer certificate file has a loading error.
16#00d0 16#0000_0003 Both certificate files have a loading error.
16#00d0 16#0000_0004 No resources for the TLS session.
16#00d0 16#0000_0005 Unknown error during TLS handshake.
Table 17 - Common Error Codes (Continued)
Error Code Extended Error Code Description