SQ-1304: Metadata Sync Failure

Description

This error occurs when the metadata sync for a datasource fails. The metadata sync calls a connector’s index method, which is most often the source of the metadata sync failure. It is typically identified in the logs of the connector, either through the View Logs function within Seeq or by reviewing the log file on the Seeq Remote Agent. It’s helpful to use the View Logs button from the Datasource administration console to narrow the logs returned to only those related to the datasource where the problem is occurring. You can also prepend the Thread contains field with Metadata Sync: to see only the logs related to the indexing process.

Possible Causes and Troubleshooting Steps

Network Issues

Ensure there are no network issues between the remote agent and the Seeq Server. Check connectivity and any firewall settings that may be affecting communication.

Datasource, Connector, or Seeq Issue

Review the log files to determine the source of the issue:

1. Datasource: Check if the datasource is functioning as expected. If the datasource is the cause, the “stack trace” for the error message will include references to the datasource’s client library, e.g. OSIsoft.AF.Asset.<etc>. In such a case, check the datasource using vendor-provided clients from the remote agent host to determine if the problem is also happening with other clients besides the Seeq connector. If so, you may need to resolve a configuration, security, or network issue with the datasource and may need to contact the support team of the datasource vendor.

2. Connector: Investigate the connector logs for any anomalies or errors. A common example might be a NullReferenceException. If the connector is the cause, it’s likely intervention from Seeq support will be needed to resolve the issue.

3. Seeq: If the problem is related to non-network issues in communicating with the Seeq site, it is likely you will see an ApiException in the error message. In this case as for a connector issue, a support ticket is likely necessary to resolve the issue.