Communication Driver error messages

Logger Message

Explanation

Probable Cause

Solution

Internal Error: CIoVariant::Update()

The internal type conversion encounters an invalid or unknown type.

This is an internal program error.

Turn on POLL_TRACE in the Logger to obtain additional trace information. Report the error to Wonderware Technical Support.

Send fail because of wrong order id

The message cannot be sent to the PLC because of the order ID is incorrect.

This is an internal program error.

Turn on POLL_TRACE, POKE_TRACE, and CYCLIC_TRACE in the Logger to obtain additional trace information. If the problem persists, report it to Technical Support.

(%d):s7_multiple_read_req (orderid=%d) [(%d) %s]

The poll message cannot be sent to the PLC.

This is an internal program error.

Turn on POLL_TRACE in the Logger to obtain additional trace information. If the problem persists, report it to Technical Support.

Internal state error: multiple read response (S7Type 0x%X)

The server receives a duplicate response for the poll message.

This is an unknown error.

Turn on POLL_TRACE in the Logger to obtain additional trace information. If the problem persists, check with the PLC vendor.

(%d):Invalid item name: %s (%s)

The requested item name has a bad syntax.

The item syntax is wrong.

Correct the item syntax as defined in this user’s guide.

(%d):Invalid item name suffix: %s (%s)

The requested item suffix has a bad syntax.

The item suffix is wrong.

Correct the item suffix as defined in this user’s guide.

Alarm event header key not: FF09: %02X%02X

The alarm received from the PLC has a bad header.

This is a PLC issue.

Turn on ALARMS_AND_EVENTS_TRACE in the Logger to obtain additional trace information. Report the error to Wonderware Technical Support.

Send: (MSG_FAIL): message (%s msg=0x%08X) [msg_state=%d,con_state=%d]

The server fails to send the message to the PLC.

This is an internal error.

Turn on POLL_TRACE, POKE_TRACE, and CYCLIC_TRACE in the Logger to obtain additional trace information. Report the error to Technical Support.

(%d): s7_brcv_init (r_id=%d)[(%d) %s]

There is an error in s7_brcv_init (Block services).

A configuration or communications error occurred.

Turn on BLOCK_TRACE in the Logger to obtain additional trace information. Report the error to Technical Support.

Timeout for initial values of block with r_id=%d

The block message has timed out for the initial updates.

The PLC does not send the block update.

Check the PLC program and see the B_SEND is configured correctly.

Timeout updating values of block with r_id=%d

Timeout occurs while updating the subsequent values for the block message.

The connection with the PLC may be dropped.

Check the PLC program and see the B_SEND is configured correctly.

Release blockid:%d for message (%s msg=0x%08X,con=%s) [number of blockids=%d] was not successful

Releasing the block ID from the block message operation fails.

This is an internal error.

Turn on BLOCK_TRACE in the Logger to obtain additional trace information. If the error persists, report it to Technical Support.

S7BlockMessage:: HandleResponse: premature block end received at size %d (expected: %d)

The message received from the PLC for the block service has no data.

This is an unknown error.

Turn on BLOCK_TRACE in the Logger to obtain additional trace information. Report the error to Technical Support.

S7BlockMessage:: HandleResponse: unsegmented block messages did not have correct size: %d (len: %d)

The unsegmented message received from the PLC for the block service has incorrect data size.

This is an unknown error.

Turn on BLOCK_TRACE in the Logger to obtain additional trace information. Report the error to Technical Support.

S7BlockMessage:: HandleResponse: segmented messages did not add up correctly in size: %d to indicated response data (len: %d)

The segmented message received from the PLC for the block service has incorrect data size.

This is an unknown error.

Turn on BLOCK_TRACE in the Logger to obtain additional trace information. Report the error to Technical Support.

S7BlockMessage:: HandleResponse: cannot allocate memory for response data (len: %d)

The server cannot allocate the memory for the response received from the PLC for the block message.

The server runs out of memory.

Turn on BLOCK_TRACE in the Logger to obtain additional trace information. Restart the server or the computer.

S7BlockMessage:: HandleResponse: too much block data received: (received: %d + new: %d more than expected: %d)

The server receives too much data for the block message.

This is a PLC problem.

Turn on BLOCK_TRACE in the Logger to obtain additional trace information. Report the error to Technical Support.

Internal Error: Unknown type: %d updating event item: %s

The server receives the updates for the unknown type of alarm and event message.

This is an unknown error.

Turn on ALARMS_AND_EVENTS_TRACE in the Logger to obtain additional trace information. Report the error to Technical Support.

Could not generate data for item %s

The server cannot read the poke value for the item.

This is an internal error.

Turn on POKE_TRACE in the Logger to obtain additional trace information. Report the error to Technical Support.

Can't send request for msg=0x%08X (no orderid available)

The server cannot send the message to the PLC because it runs out of order IDs.

This is an unknown error.

Turn on POLL_TRACE, POKE_TRACE, and CYCLIC_TRACE in the Logger to obtain additional trace information. Report the error to Technical Support.

Send fail because of wrong order id

The server cannot send the message to the PLC because the order ID is incorrect.

This is an unknown error.

Turn on POLL_TRACE, POKE_TRACE, and CYCLIC_TRACE in the Logger to obtain additional trace information. Report the error to Technical Support.

(%d): s7_multiple_write_req (orderid=%d) [(%d) %s]

The write request to the PLC fails.

The data poke may be too long or this is an internal error.

Turn on POKE_TRACE in the Logger to obtain additional trace information. Report the error to Technical Support.

Internal state error: multiple write response (S7Type 0x%X)

The server receives a duplicate response for the poke message.

This is an unknown error.

Turn on POKE_TRACE in the Logger to obtain additional trace information. If the problem persists, report the error to Technical Support.

(%d): s7_cycl_read_init_req (orderid=%d) [(%d) %s]

An error occurs when sending the S7 cyclic read initiation request message.

A configuration or communications error occurred.

Check the PLC configuration/connection and resource limitation, particularly the ones related to the cyclic servce.

(%d): s7_cycl_read_start_req (orderid=%d): [(%d) %s]

An error occurs when sending the S7 cyclic read start request message.

A configuration or communications error occurred.

Check the PLC configuration or connection.

(%d): s7_cycl_read_delete_req (orderid=%d): [(%d) %s]

An error occurs when sending the S7 cyclic read delete message.

A configuration or communications error occurred.

Check the PLC configuration or connection.

ERROR in S7_CYLC_READ_INIT_CNF - PLC responded with error code

The PLC returns an error code in response to the cyclic read initiation request.

It is a PLC, Communication Driver configuration, or resource error.

Turn on CYCLIC_TRACE in the Logger to obtain additional trace information. Check the PLC configuration/connection and resource limitation, particularly the ones related to the cyclic service.

ERROR in S7_CYCL_READ_START_CNF - PLC responded with error code

The PLC returns an error code in response to the cyclic read start request.

It is a PLC or Communication Driver configuration error.

Turn on CYCLIC_TRACE in the Logger to obtain additional trace information. If the problem persists, contact Technical Support.

ERROR in S7_CYCL_READ_DELETE_CNF - PLC responded with error code

The PLC returns an error code in response to the cyclic read delete request.

It is a PLC or Communication Driver configuration error.

Turn on CYCLIC_TRACE in the Logger to obtain additional trace information. If the problem persists, contact Technical Support.

Internal state error: cyclic read response (S7Type %d -> 0x%X)

The server receives a duplicate response for the cyclic message.

This is an unknown error.

Turn on CYCLIC_TRACE in the Logger to obtain additional trace information. If the problem persists, contact Technical Support.

Scan event header key not: 120A: %02X%02X

When parsing the packet returned by the Scan event packet from the PLC, the header key is incorrect.

This is a programming error.

Turn on ALARMS_AND_EVENTS_TRACE in the Logger to obtain additional trace information. Repeat the test and/or restart the Communication Driver/PLC. If the error persists, contact the PLC vendor.

Item doesn't fit in a single message and won't be advised

The server cannot fit this item into a message, therefore it cannot advise this item.

The item byte range is larger than the PLC PDU size.

Split the item into smaller items so that they can be fitted into the available PDU size (480 bytes).

Can't create poke message for item %s, data size is too large

The server cannot fit this item into a poke message, therefore it cannot poke this item.

The item byte range is larger than the PLC PDU size.

Split the item into smaller items so that they can be fitted into the available PDU size (480 bytes).

Can't create poke message for item %s, not able to generate data

The poke data for creating a poke message cannot be generated.

The poke data value cannot be converted into the PLC datatype.

Check the value being poked and create the correct format.

,%s, Leaving Slow Poll Mode

This is only a piece of information about the server leaving the Slow Poll mode.

The connectivity to the PLC recovered from a failure. Normal communications is resumed.

If this message shows up consistently, verify the network connectivity to the PLC.

,%s, Entering Slow Poll Mode

This is only a piece of information about the server entering the Slow Poll mode.

The connectivity to the PLC failed. The Communication Driver tries to reconnect at the Slow Poll interval.

Verify the network connectivity to the PLC. Turn on CONNECTION_TRACE, DASSend, and DASReceive in the Logger to obtain additional diagnostic information.

TIMEOUT for pending initiate request

A timeout occurs while waiting for an initiate confirmation.

A configuration or communications error occurred.

Check the communications or configuration. If the problem persists, turn on CONNECTION_TRACE, DASSend, and DASReceive in the Logger to obtain additional diagnostic information.

(%d):s7_initiate_req [(%d) %s]

There is an error in initiating a request (establishing a connection).

A configuration or communications error occurred.

Check the connection and the PLC configuration/ program. If the problem persists, turn on CONNECTION_TRACE, DASSend, and DASReceive in the Logger to obtain additional diagnostic information.

Can't connect

There is an error establishing a connection.

A configuration or communications error occurred.

Check the connection and the PLC configuration/program. If the problem persists, turn on CONNECTION_TRACE, DASSend, and DASReceive in the Logger to obtain additional diagnostic information.

Received order id on a deleted non read/write (type: 0x%04X) message: 0x%x

The server receives a response from the PLC for a message that has already been deleted from the server.

Unexpected order ID is received from the PLC. The Communication Driver discards the message associated with it.

If the problem persists, contact the PLC vendor.

Generate data failed for item %s because at least one element of the array is not filled

The server cannot poke the array item as the items are not filled correctly.

You poke the array items but some of the element are left unfilled. All elements in the array are rejected for poking.

Fill all elements in the array before poking the array.

TIMEOUT for connection (while %s), m_state=%d

A timeout occurs while waiting for a response message to <command>.

A communications/ configuration error occurred.

Verify the network connectivity to the PLC. Turn on CONNECTION_TRACE, DASSend, and DASReceive in the Logger to obtain additional diagnostic information.

(%d): s7_msg_initiate_req (orderid=%d) for %s [(%d) %s]

There is an error in the message initiate request (initiating alarms and events).

A configuration or communications error occurred.

Verify the network connectivity to the PLC. Turn on CONNECTION_TRACE, DASSend, and DASReceive in the Logger to obtain additional diagnostic information.

ERROR: order ID %d exists for cyclic ID: %d in cyclic reference map

The server tries to add the order ID for the cyclic service that has already been occupied by some other message.

This is an internal error.

If the problem persists, turn on CYCLIC_TRACE in the Logger to obtain additional diagnostic information.

ERROR: Retrieving order ID: %d from cyclic ID: %d in cyclic reference map

The server cannot find the order ID in the order ID map for this message.

This is an internal error.

If the problem persists, turn on CYCLIC_TRACE in the Logger to obtain additional diagnostic information.

ERROR: UNKNOWN cyclic ID (%d) in cyclic read indication

The server receives an unknown cyclic message form the PLC.

The PLC reports a cyclic response that is not requested by the Communication Driver.

Check with the PLC vendor.

,%s, Connection aborted

The connection to the PLC is closed.

Either the PLC closed the connection or the server closed the connection.

If this is caused by the normal shutdown or items removal, no actions are required. If not, verify the PLC configuration for the Keep-Alive parameter.