
150
Rockwell Automation Publication 2080-UM002N-EN-E - November 2022
Chapter 8 EtherNet/IP Network
0x0107
Connection Request Error:
Target Connection Not Found.
A connection being accessed was not found.
Possible causes include the following:
• You have configured module to use a unicast connection
over EtherNet/IP network, but the producer does not
support unicast connections.
• The module in use (that is, the physical module) is
different than the module specified in the I/O
configuration tree and is therefore causing the
connection or service to fail.
• The fault may occur even when the module passes the
electronic keying test. This may result when Disable
Keying or Compatible Keying options were used in the
module configuration instead of the Exact Match option.
• Despite passing the electronic keying test, the module
being connected to does not have the same features or
settings as the module specified in the I/O configuration
tree and does not support the connection or service being
attempted.
Check the module in use and verify that it exactly matches
the module that is specified in the application. For more
information about electronic keying, see the user manual
for the module you are using.
0x0108
Connection Request Error:
Connection type (Multicast/
Unicast) not supported.
The controller is requesting a connection type that is not
supported by the module.
Possible causes include the following:
• You have configured the module to use a unicast
connection over EtherNet/IP network, but the producer
does not support unicast connections.
• The module in use (that is, the physical module) is
different than the module specified in the I/O
configuration tree and is therefore causing the
connection or service to fail.
• The fault may occur even when the module passes the
electronic keying test. This may result when Disable
Keying or Compatible Keying options were used in the
module configuration instead of the Exact Match option.
• Despite passing the electronic keying test, the module
being connected to does not have the same features or
settings as the module specified in the I/O configuration
tree and does not support the connection or service being
attempted.
Check the module in use and verify that it exactly matches
the module that is specified in the application. For more
information about electronic keying, see the user manual
for the module you are using.
0x0109
Connection Request Error:
Invalid connection size.
The connection size is inconsistent with the expected size.
Possible causes include the following:
• The controller is attempting to set up a connection with
the module and cannot because the size of the
connection is invalid.
• The module in use (that is, the physical module) is
different than the module specified in the I/O
configuration tree and is therefore causing the
connection or service to fail.
• The fault may occur even when the module passes the
electronic keying test. This may result when Disable
Keying or Compatible Keying options were used in the
module configuration instead of the Exact Match option.
• Despite passing the electronic keying test, the module
being connected to does not have the same features or
settings as the module specified in the I/O configuration
tree and does not support the connection or service being
attempted.
• Check the module in use and verify that it exactly
matches the module that is specified in the application.
For more information about electronic keying, see the
user manual for the module you are using.
• If the module is a 1756 ControlNet® module, verify that the
chassis size is correct. For remote I/O adapters, verify
that the rack size and rack density are correct.
0x0110
Connection Request Error:
Module not configured.
The controller is attempting to set up a Listen
Only
connection with the module and cannot because the module
has not been configured and connected to by an owner (for
example, another controller).
This controller is not an owner of this module because it is
attempting to establish a Listen Only connection, which
requires no module configuration. The controller cannot
connect until an owner configures and connects to the
module first.
Table 25 - List of Connection Fault Codes (Continued)
Fault Code
Display Text
Fault
Corrective Action