Error diagnosis

This documentation article explains some common configuration or setup mistakes and could be a good way to troubleshoot your setup. Creating an Error logging could also be helpful.

Behavior

Description

The icon in the taskbar turns RED after startup

Check all settings again and enable the Error logging. Also check the following:

  • Can the TC3 IoT Data Agent connect to all configured gates (see below)?
  • Are there enough licenses?

Connection to the MQTT message broker could not be established

Check the following:

  • Make sure that the message broker is accessible for the device on which the TC3 IoT Data Agent is running. The MQTT standard port is 1883/tcp for unencrypted MQTT communication and 8883/tcp if MQTT-TLS is used. Make sure that these ports are open in your firewall (on the message broker side for incoming access and on the TC3 IoT Data Agent side for outgoing access).
  • Make sure that you are using the correct access data (if applicable) for the message broker
  • Check the connectivity with the message broker by using another MQTT client, e.g. Mqtt.Fx, MqttSpy or the Mosquitto command line tools.

Connection to ADS device could not be established

Check the following:

  • Make sure that you use the correct ADS port and AmsNetID for the remote device
  • Make sure that there are no firewall settings on the remote device that prevent ADS access.
  • Make sure that the computer on which the TC3 IoT Data Agent is running has an ADS route configured for the corresponding TwinCAT target device. (Only applicable if the TC3 IoT Data Agent and the ADS target runtime are located on different computers).

Connection to OPC UA server could not be established

Check the following:

  • Make sure that there are no firewall settings on the computer on which the OPC UA server is running that prevent remote access to the server.
  • Check any local firewall settings on the TC3 IoT Data Agent device.

Connection to Azure IoT Hub could not be established

Check the following:

  • Make sure that you use the correct IoT Hub host name
  • Make sure that you have created a device on Azure IoT Hub, e.g. by using the Azure IoT Explorer, and that you have entered the correct device data for this device in the TC3 IoT Data Agent configurator
  • Make sure that you have used the correct CA certificate for Azure IoT Hub and that the CA certificate is used in a Base64-encoded file format.
  • Make sure that you do not use the same access data on another device. Only one connection to IoT Hub can be established with the same set of access data.

Connection to AWS IoT could not be established

Check the following:

  • Check the connectivity with AWS IoT by using another MQTT client, e.g. Mqtt.Fx, MqttSpy or the Mosquitto command line tools.
  • Make sure that no firewalls are blocking the TCP port 8883 (outgoing), which is required for connectivity with AWS IoT.
  • Make sure that you have used the correct set of certificates (as supplied by the AWS IoT management website)

The error message "InvalidServerCert" is displayed

This error message means that the Data Agent encountered a problem while checking the server certificate and the check was not successful. Reasons for this can be, for example:

  • The CommonName or the Subject Alternative Name (SAN) in the server certificate is not the same as the address used for the connection to the server.
  • The server certificate has expired.

The server certificate could not be validated, although the correct CA certificate was referenced.

Some operating environments use a so-called CA chain, consisting of root and one or more intermediate CAs. In this case, the CA certificate referenced in the Data Agent must contain the complete CA chain so that the server certificate can be checked correctly.