TN Hist0318001Data not being logged to a remote historian after configuration in the IDE
Last updated: March 18th, 2026Description
- Author: Zach Burns
- Published: March 18th, 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!
Give feedback about this article
Recommended articles
[ISS Support Case] Cannot connect to the historian
After tag reimport, the historian keeps disconnecting/reconnecting
Read More[ISS Support Case] Historian Missing Tags
Client called in due to noticing they were missing around 37,000 tags and only had around 7,000 showing in system since yesterday afternoon. When inquiring about any recent changes client stated that they were attempting a bulk import yesterday when they received an error. They are unsure of the exact error but client stated it was something along the lines of "Cannot reserve the .LOK file." They believed the error was due to a lack of space/memory or too many nodes in the importer so they deleted 10-15 of the nodes which I believe were tied to the missing 37,000 tags. Attempted to query some of the missing tags using query and no data was returned for tags for live or historical values. Believe that nodes will be need to be readded to import tags or possible backup restoration on system?
Read More[ISS Support Case] Historian Client Unable To Add Server In Server List Configuration
Under Server List Configuration Failed to connect: Unable to reach INSQL/Historian server, make sure that INSQL/Historian server is running
Read More