Historian troubleshooting

Overview

This Historian Module relies on other modules when storing the data. For instance, for SQL targets, the final database insertion is executed by the Dataset Tag provider; for external database, such as Canary or Tag Provider Historian tools, the related third party system will perform the access.

Therefore, many potential issues regrind data storage are not at the Historian Module level, but related to the external database repository, which requires diagnostics with other specific tools, according to the Target Database.

The execution status of the Historian module itself, can be easily monitored using the Module Information diagnostic tools, and the Trace Window tool as described in this Section. 

Resolving Common Problems

Using the  Diagnostics Tools

Monitoring Execution Status Within the Application

Module Information - Historian Properties

The diagnostic tool Module Information updates in real-time advanced information about the Execution of the Historian Module.

By running the ModuleInformation.exe tool, the section Historian updates the following properties:

The names of properties are self-explanatory, but in many cases, its exact meaning requires a deeper understanding of the implementation of the module. Contact technical support sending the contents of the table for specific analysis. 

When selecting one Specific HistorianTable in the Tree under Historian, the following information is available:

TraceWindow - Historian 

The TraceWindow diagnostic tool provides real-time logging of events connected with the Historian Module execution. 

Four level of message can be enabled.

In this section...