TN - AppSrv - 26051811 Could not resolve reference; (myengine.engine.historian.connection)
Last updated: May 21st, 2026Description
- Author: Sam Soens
- Published: May 21st, 2026
Details:
- Document Version: 001
- Applies to Version(s): All versions up to and including 2023x
Description
This Technote outlines an error sometimes seen with Application Server object graphics and a common resolution.
A graphic may not work properly, and in Log Viewer you might find:
Could not resolve reference; (myengine.engine.historian.connection)
Solution Steps:
The graphic should be part of an object under the engine referenced. Ensure the graphic is not standalone in the Graphic Toolbox. If it is not tied to an object assigned to the engine, it will not be able to resolve the myengine reference.
Secondly, make sure the hosting engine is configured to Historize. If it isn't, it can also throw this error message.
_____________________________________________________________________________________________________
Give feedback about this article
Recommended articles
[ISS Support Case] Not writing to historian
2 platforms not writing to historian. please update historian server properties with valid credentials
Read More[ISS Support Case] Historian Data Importer Failure
Client reached out as when attempting to import any CSV data into the Historian data importer it fails with the same error message: "Error processing the file. Error in line number 2. Unsupported delimiter." This was tested with multiple unique CSV's exported from both Query and Trend.
Read More[ISS Support Case] Historian missing data
A month ago they changed the network acct utility. Missing data from 9/7 - 10/30, data starting coming in after they re-ran the change network acct utility again. ?Using tiered historian.
Read More