ABCIP Communication Driver error codes and error messages

Error codes

There are two server-specific error codes, shown in the following table, that augment those provided by the Operations Integration Toolkit.

Error messages

The following table lists the error messages produced by the Communication Driver that are logged to the Log Viewer.

• <Message ID> corresponds to the message ID displayed in the Communication Driver’s Diagnostics root in the OI Server Manager.

• <Device> refers to the node name of the device.

  Note: All of the error messages shown in the following table apply to the DASProtFail log flag.

  Error Message	Explanation	Probable Cause	Solution
  A PLC (IP:<IPAddress>) attempted to send us an unsolicited data packet. But the maximum number of simultaneous unsolicited data connections [MAX socket] has already been reached. Data packet ignored.	The maximum number of sockets used for unsolicited data communications has been reached. No more unsolicited data packages will be accepted.	The maximum number of sockets used for unsolicited data communications has been reached.	Decrease the number of unsolicited data to communicate to the socket.
  ABCIPAcceptedSocket: Initialize unable to associate an event with a handle	Unable to associate the event with a valid handle within the internal state computer.	Software internal error.	Restart the Communication Driver and try again.
  Array index error found while formatting message for block <Block Number>	The Bit number specified in the item is out of range	Bit number is out of range	Verify and specify the correct bit number appropriate for the data type of the item tag.
  Attempt to resolve remote hostname <HostName> failed	Failed to resolve the HostName.	The HostName cannot be translated to a valid IP address internally.	Check if the HostName is configured correctly in the server.
  Cannot create optimize structure for item <Item Name> message <MessageID>	The server failed to create internal structure.	It is an internal error.
  Connection to <Target Address> on port <Port Number> failed with error <Error Code>.	Error is returned from the OS while trying to establish the socket connection.	Indicated by OS returned <Error Code>.
  Connection to <Target Address> on port <Port Number> refused.	No connection can be made because the target device actively refused it.	The target address is not a ControlLogix Ethernet Module.	Check the device configured with the address.
  Encountered the following error in reply message <Message ID> when reading from <Device>	Error codes are returned in the poll-message response from the device; further explanations follow.	Depends on the CIP errors returned (refer to the tables in Logix5000 Error Codes).	Check to see if there are other error messages in the logger. Check the Communication Driver diagnostics, if necessary.
  Encountered the following error in reply message <Message ID> when writing to <Device>	Error codes are returned in the poke-message response from the device; further explanation follows.	Depends on the CIP errors returned (refer to the tables in Logix5000 Error Codes).	Check to see if there are other error messages in the logger. Check the Communication Driver diagnostics, if necessary.
  Encountered the following error when reading block <Block Item Name> in message <Message ID> from <Device>	Error codes are returned in the request block for Multi-Request messages. Further explanation of the errors will be listed.	Depends on the CIP errors returned (refer to the tables in Logix5000 error codes).	Check to see if there are other error messages in the logger. Check the Communication Driver diagnostics, if necessary.
  Encountered the following error when reading optimized block <Internal Block Address> in message <Message ID> from <Node>	The error code is returned from the ControlLogix controller when the server tries to read the optimization structure in the controller.	This is an internal error. See the CIP Service error code for details.
  Encountered the following error when writing block <Block Item Name> in message <Message ID> from <Device>	Error codes are returned in the request block for Multi-Request messages. Further explanation of the errors will be listed.	Depends on the CIP errors returned (refer to the tables in Logix5000 error codes).	Check to see if there are other error messages in the logger. Check the Communication Driver diagnostics, if necessary.
  Error encountered initializing Unsolicited Data Port. No direct (i.e.: peer-to-peer) unsolicited data will be accepted.	There is a failure to create a listening socket for the peer-to-peer unsolicited data used. As a result, no unsolicited data can be accepted.	Another application has already been listening at the same port. The network communications is having a problem. The controller is having a problem communicating.	Make sure that no other application is running and listening at the same port (such as RSLinx). Make sure the network is functioning. Make sure the controller is functioning.
  ExtSTS=<Extended Error Code>: <Description>	The error message shows the extended CIP error code and description, if there is one.	CIP-error dependent (refer to the tables in Logix5000 error codes).
  Failed to add block <block number> with base name <UDT base name> in <PLC address>, tag does not exist in the PLC or some of its UDT members are configured for External Access=None in the PLC	The error message shows when advising a UDT member with external access set to NONE or the PLC tag does not exist.	Either the tag does not exist in the PLC or one or more UDT members are configured for an External Access attribute of "None".	Set the UDT member external access from NONE to Read Only or Read/Write, or create the tag.
  Failed to initialize Listen Socket (CIP port = <Port Number>)	Listening socket with the indicated port number is being used by another process. ABCIP Communication Driver cannot receive unsolicited message from controllers.	There may be third party products already listening on the same CIP port.	Shut down any third-party product (such as RSLinx) listening on the same CIP port and restart ABCIP Communication Driver.
  Host EtherNet/IP <IP address> connect host failed, maximum number of socket <MAX socket> exceeded	The maximum number of sockets allowed was exceeded.	The maximum number of sockets allowed was exceeded.	System limit on TCP sockets on the machine hosting the Communication Driver is reached. Check if there are other programs on same the machine consuming a large number of sockets.
  Inconsistent message type encountered for <Device Name>	The Communication Driver encounters an internal error.	This is an internal error.
  Invalid item <Item Name> fields required for structure item	UDT member was not defined in the item syntax	Invalid Item syntax	Specify the member of the UDT structure in the item tag
  Invalid item <Item Name> bit number not allowed or invalid	The Bit number specified in the item is out of range or invalid	The bit number is specified for a non-integer type.	Verify and specify the correct bit number appropriate for the data type of the item tag.
  Invalid item <Item Name> structure not found	Specified UDT structure does not exist in the controller	Invalid item syntax	Verify if the UDT structure name is correct and exists in the controller.
  Invalid item <Item Name>, invalid item format <format>	"," was used to specify the item’s format. However, the format was found to be invalid for the item.	An incorrect format was used for the item.	Check the item’s format.
  Invalid item <Item Name>, invalid index	An invalid index is specified in the item.	An invalid index is found in the item.	Check the index specified. Only integer is accepted as an index.
  Invalid item <Item Name>, member <Member Name> not found in structure	The member of the structure cannot be found.	The member is not defined in the structure.	Check the structure’s definition in the device.
  Invalid item <Item Name>, not defined in the processor	The item’s definition cannot be found in the tag database.	The item is not defined in the Logix processor.	Check the item’s definition in the device.
  Invalid item <Item Name>, offset dimension exceeded	The internal limit of the item’s nesting level (20) was exceeded. In general, each "." and the index [x] increment the item’s nesting level by 1.	The item’s nesting level exceeds the server’s limit.	Reduce the item’s nesting level.
  Invalid item <Item Name>, retrieving whole structure not supported	The item points to a structure other than a string. The Communication Driver does not support this type of item.	A structure item is specified.	Retrieve an individual member of the structure instead of the whole structure.
  Invalid item <Item Name>, structure not found	The structure definition for the item cannot be located.	Invalid item encountered.	Check the item’s definition in the device.
  Invalid item <Item Name>, syntax error	There is a syntax error in the item.	An invalid item is specified.	Check the item’s syntax.
  Invalid item <Item Name>, unknown suffix	The suffix specified after "," is not recognized by the Communication Driver.	The suffix is not supported.	Check the suffix specified for the item.
  Invalid item <Item Name>, dimension mismatch	The dimension specified in the <Item Name> is different from what has been defined in the device.	The item’s array dimension is different from the definition in the device.	Check the item’s definition in the device.
  Invalid item <Item Name>, index bracket mismatch	The bracket for the index is mismatched. This is an item syntax error.	An invalid item is entered.	Correct the item’s syntax.
  Invalid item <Item Name>, index out of range	The index specified in the <Item Name> is outside the range defined in the device.	The item’s index is too large.	Check the item’s definition in the device.
  Invalid item <Item Name>, invalid bit number	The bit number specified in the item is invalid.	An invalid item is specified.	The bit number specified cannot go beyond the range allowed for the item’s data type. For example, INT range is 0-15 and DINT range is 0-31.
  Item <ItemName> cannot be created, out of memory.	ABCIP Communication Driver failed to obtain memory during item creation.	The system ran out of memory.	Reduce the number of tags in the Communication Driver. Close other applications.
  Message <Message ID> for <Device> timed out.	The Communication Driver did not receive the message’s response from the device within the <Reply Timeout> specified.	The device is off line.	Check the device’s network connection.
  Mismatched bracket found while formatting message for block <Block Number>	Invalid item syntax	Missing bracket in the item tag	Specify the missing bracket in the item tag.
  Received packet from [HostName] too big on port [PortNumber] ([#of bytes received] bytes)	The received packet from the controller exceeds the maximum packet size allowed for this type of protocol.	Incorrect data packet was read from the socket.	Check if the server is configured properly for the target ControlLogix controller.
  Received incomplete response packet for message <Message ID> from <Device>	The response packet is incomplete or corrupted.	Bad connection or there is a Communication Driver problem.	Check if there are other error messages in the logger. Check the OI Server diagnostics if necessary.
  recv() for <HostName> on port <PortNumber> failed	Failed to read from the Window Socket specified.	Failed to read from the Winsock.	Repeat the operation by restarting the Communication Driver.
  Register Session encountered the following error: recd packet from [HostName] too big on port [PortNumber] ([#of bytes received] bytes)	The Communication Driver encountered an error while trying to establish an EtherNet/IP session with the controller. The received packet from the controller exceeds the maximum packet size allowed for this type of protocol.	Not communicating with a ControlLogix controller. Incorrect data packet was read from the socket.	Check the controller configuration. Check if the server is configured properly for the target ControlLogix controller.
  Rejected %s ITEM = %s on plc %s	The item cannot be added or subscribed from the OI Server. The time tag portion in the &T& syntax is missing or invalid.	The time tag portion in the &T& syntax is missing or invalid.	If the &T& syntax is used, make sure that it consists of a valid data tag followed by the "&T&" and a valid time tag.
  Rejected <PLC Type Name> ITEM = <Item Name> on plc <PLC Node Name>. Time Tags not supported on Firmware Revision less than 16.0	The &T& time tag syntax cannot be used with controller firmware prior to version 16.0.	Controller firmware version is not compatible with &T& time tag requirement.	Upgrade the controller firmware version to 16 or above if the &T& time tag syntax is to used.
  Rejected <PLC Type Name> ITEM = <Item Name> on plc <PLC Node Name>. Invalid data type for time tag	The data type of the time tag is not correct	The data type of the time tag is not correct	The data type for time tag must be LINT
  Response service code <ServiceCode> different from command <Service Code> for message <Message ID>	The service code in the message sent does not match the one in the reply.	Packet corrupted or OI Server problem encountered.	Check if there are other error messages in the logger. Check the Communication Driver diagnostics, if necessary.
  Response service code <ServiceCode> not handled	Unexpected service code was encountered in the reply packet from the controller.	This is an internal error.	The service code received by the Communication Driver is not supported. Verify the controller firmware version against version supported by the Communication Driver.
  Session error <Error Code>, packet ignored	Communications errors encountered.	CIP-error dependent (refer to the tables in Logix5000 error codes).
  Socket <SocketID> send() returned <ErrorNumber>, connection to be closed	This is an internal Winsock error.	This is an internal Winsock error.
  Socket <SocketID> sending packet with buffer size <BufferSize> larger than <MAX buffer size>	Failed to send on socket due to the data packet size.	This is an internal error.
  STS=<CIP Error Code>: <Description>	The error message lists the CIP error code and description.	CIP-error dependent (refer to the tables in Logix5000 error codes).
  Timeout waiting for an unknown event from PLC on an unsolicited data port connected to <PLC Host Name>	Timeout occurred while waiting for unsolicited data packet from a controller.	Failed to receive unsolicited data from a controller.	Make sure the controller is configured to send out unsolicited data correctly. Make sure the Communication Driver is functioning correctly.
  Timeout waiting for data packet from PLC on an unsolicited data port connected to <PLC Host Name>	Timeout occurred while waiting for unsolicited data packet from a controller.	Failed to receive unsolicited data from a controller.	Make sure the controller is configured to send out unsolicited data correctly. Make sure the Communication Driver is functioning correctly.
  Timeout waiting for initialization packet from PLC on an unsolicited data port connected to <PLC Host Name>	Timeout occurred while waiting for unsolicited data header from a controller.	Failed to receive unsolicited data from a controller.	Make sure the controller is configured to send out unsolicited data correctly. Make sure the Communication Driver is functioning correctly.
  Unsolicited socket not open for device <Device>	Unsolicited socket was not open when the Communication Driver tried to send a reply message to the device.	This is an internal error.	Reset the node hierarchy to restart the connection