Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Historian

System messages

  • Last UpdatedFeb 27, 2025
  • 2 minute read

System messages include error messages and informational messages about the state of the AVEVA Historian as a whole or for any of the internal subsystems and individual processes.

System messages are logged to these places:

  • ArchestrA Logger

  • Windows Event Log
    You can view this log with the Windows Event Viewer. Not all messages are logged to the Windows event log. In general, only user actions and exceptional events are written to this log. The messages are logged with the "Historian" or the name of the AVEVA Historian service as the source.

System messages are divided into the following categories:

Category

Description

FATAL

The process cannot continue. An error of this severity results in a system shutdown.

CRITICAL

These types of errors will cause malfunctions in the data storage or retrieval systems, such as data loss or corruption.

ERROR

General errors. For example, address validation errors during system startup. These errors may result in an orderly shutdown of the system, but will not preclude system operation in most cases.

WARNING

Messages that simply notify the operator of parameter settings or events that have occurred. For example, failure to link a dynamically-linked procedure entry point for a non-obligatory function will be logged as a warning.

INFO

Messages relating to startup progress or the commencement of active data storage.

DEBUG

Debugging messages, which will not typically appear in released versions of the system.

AVEVA Historian messages are logged to the Log Viewer as follows:

  • Critical, fatal, and error messages are logged as "Error" messages. The appropriate indicator, either "CRITICAL," FATAL," or "ERROR," will be prefixed to message.

  • Warnings will be logged as "Warning" message, with no prefix.

  • Informational messages will be logged as "Info" messages, with no prefix.

  • Debug messages will be logged as "Trace" messages, with no prefix.

For information on monitoring the system, see Monitoring the System.

TitleResults for “How to create a CRG?”Also Available in