Data not being logged to a remote historian after configuration in the IDE
Last updated: March 3rd, 2026Description
- Author: Zach Burns
- Published: March 3rd, 2026
Details:
Problem: During a new installation of System Platform, after configuring the Platform AppEngine to historize data, we are not seeing any data in the remote historian. We have followed the AVEVA instructions exactly as written and have triple-checked that our configuration is correct! The following error is observed in the OCMC logger on the client node:
Error = 256 (Certificate not found)

By default, the application engine configuration is configured to “require a trusted certificate”. In galaxies where SMS has not yet been configured, this setting will prevent data from being logged to a remote historian that does not have an installed valid certificate.
To fix this issue double click the application engine object to open the configuration editor. Expand the "Advanced settings" section under the General tab and select the option for “Accept an untrusted certificate (NOT RECOMMENDED)”. Data will now by logged to the Historian and no certificate errors will be observed in the OCMC logger on the Historian or client machine.

Alternatively, you can designate a machine in the Galaxy as the System Management Server and configure the certificate on all nodes in the Galaxy. This will also resolve the issue and enable encrypted communication between Galaxy nodes!