Installing Alarms and Events

About this task

Selecting the Install Alarms and Events option in the Install Historian screen installs the Historian Alarm Archiver. You must specify the SQL Server database details for the archiver, as the archiver requires access to SQL Server.
  • If you have the Alarms and Events component installed on a pre-7.0 version of Historian, then after you upgrade to Historian Server 7.0, you must install the Alarms and Events component separately.
  • The Alarms and Events component must be installed on the same machine as the Data Archiver.
  • When upgrading from 4.5 to 7.0 Alarms and Events, since the DB Schema for 4.5 is different, if you select the same database name that is pre-populated by default, you will get an error message: Later or Higher version of Alarms and Events database is already installed. Hence, you cannot proceed further. You need to enter a different database name and then proceed with the upgrade.

To install Alarms and Events:


  1. Run the Historian install.
    The Historian splash screen appears. If this screen does not automatically appear, double-click the InstallLauncher.exe file on the ISO or DVD to display it.
  2. Click Install Alarms and Events.
    The Alarm and Event Archiver screen appears. The Server Name and Database Name fields might be auto-populated with default values.
  3. To change either of these fields, type a different entry in the respective text box.
    The Server Name is where SQL Server is installed and the Database Name is for the database where the alarms and events are archived.
  4. Select the box for Use SQL path as data and log path and enter the SQL Server login credentials in the Admin User and Password fields.
    If you choose to use Windows Authentication, select the box for Use Windows Authentication and enter your Windows admin credentials in the Admin User and Password fields.
  5. Click Next.
    It may take several minutes for the installation to complete.
  6. If asked to restart your system, click Yes.
  7. To verify that the Alarms service has started, go to the Services window and look for the Historian Alarm Archiver.
    Startup Type is Automatic, meaning it is started automatically when the system is started or restarted.

    Historian's Alarm and Event (A&E) archiving offers the ability to collect A&E data from any OPC-compliant A&E server and store it in an integrated relational database. Historian Alarm and Event data is associated with the related process data from its source to allow for quick analysis.

    For more information, refer to Historian Alarms and Events.