Data items sent by the asset do not reach ThingWorx Platform
User Actions
The user must perform the following actions when faced with this error:
Check if thelastConnection property of the Thing is updating. If it does not update, refer to Observation 2: The lastConnection property of the Thing does not update.
Verify that the Connector is still running or attached. To do this, navigate to the Monitoring > Connection Servers page and validate that the Connector is available in the list.
Verify that the property that matches the data item of the asset exists on the Thing. Check if the property is configured to be a remote property. Verify that the property Remote Prop Name matches the data item name of the agent.
If the property does not exist, then an Invalid Property Value error will be written to the log for the ThingWorx Platform. For more information, refer to Exceptions Observed in the Log for the ThingWorx Platform. A PropertyWriteError event is also sent to the Thing. Users can then create a subscription to this event on the Thing.
Verify that the base type of the property matches the data item type of the agent.
Data Item Type of the Agent
Base Type of the property
Analog (numbers)
NUMBER
Digital (0 or 1)
BOOLEAN
String
STRING
If the base type does not match with the data item type, you will not receive any errors in the log file, but you may receive unexpected results.
For example, if the base type of the property is updated to boolean and if the data item type is set to number, then no errors are logged, but the value of the property does not update and remains at a value of true.
Check if the WritePropertyError advisory event was sent to the Connection Services Hub. This indicates that the Connector attempted to write a property for a Thing, but could not do it because of a problem.
Administrator Actions
In addition to the steps that the user performs, the administrator must perform the following steps when faced with this error:
If you are running a multi-node connector environment, verify that all the Connectors are still running or attached.
Check the Monitoring > Connection Servers page and validate that the correct number of connectors are available in the list. If all the Connectors are not displayed in the list, then traffic could land on a broken connector and it does not reach ThingWorx Platform.
Monitor metrics from the Connector nodes to validate that each eMessage Connector is processing messages from the load balancer. For more information, refer to Metrics Monitoring.
Review logs from each connector node and validate that it has not disconnected from the Platform. If exceptions are present, refer to Exceptions Observed in the Log for eMessage Connector.
Use a packet sniffer to validate that network packets are being sent:
Between the load balancer and each connector node.
Between each connector node and ThingWorx Platform.
Review the Connector logs to determine if any exceptions are present. If exceptions are present, refer to Exceptions Observed in the Log for eMessage Connector.
Check if the Connector has stopped processing messages from agents completely. For more information, refer to Observation 11: Connector stops processing agent messages completely.
Was this helpful?