Known anomalies from

FactoryTalk Edge Gateway

version 1.01.00

Redeploying a ThingWorx application that has Store and Forward enabled produces errors until the ThingWorx application finishes egressing stored data from the previous deploy. This issue occurs after deleting, renaming, or moving properties to a different node.

FactoryTalk Live Data shortcuts to OPC UA servers do not properly populate array names in

FactoryTalk Edge Gateway

data sources. Additionally, structured data types cannot egress data to

FactoryTalk Edge Gateway

applications.

There is no workaround for this issue.

FactoryTalk Smart Object

instances stop egressing to applications after 5 days. A "conversion failed CipService" error appears in the log file.

To work around this issue, restart the application that is using the data source so

FactoryTalk Smart Object

instances resume collecting data.

Deploying SQL produces an infrequent error that states that a table already exists. Data egress to SQL is not affected.

There is no workaround for this issue.

See Also