Failed (FAILED_ALM) hardware alarms

Adapter Error - data_source processing stopped from node node_name	The Batch Historian cannot process Batch Executive, Campaign Manager, or Event Chronicle data originating from the node_name node. Note This message may indicate a fault condition in the Batch Manager or Batch Historian.
Card Integrity Error - Remote Node ID, card_type Card, Cnn	An integrity problem has been detected with the remote I/O card in slot Cnn of the remote I/O node. No other errors have been detected.
Card Integrity Error - Remote Node node_name, card_type Card, Cnn	An integrity problem has been detected with the remote I/O card in slot Cnn of the node_name remote I/O node. No other errors have been detected.
Configuration Mismatch - Zone zone_name, local zone	A configuration mismatch has been detected by the local Inter-Zone Server with the zone_name zone.
Create Failure - Database could not be created	A file in which to store Alarms and Events records for the active Event Chronicle database could not be created on the ProfessionalPLUS workstation. The default location of the file for the active Event Chronicle is in the DeltaV\DVData\CHRONICLE folder.
Create Failure - Overflow database could not be created	A file in which to store Alarms and Events records for the current Event Chronicle database could not be created on the ProfessionalPLUS workstation. The default location of the file for the current Event Chronicle is in the DeltaV\DVData\CHRONICLE folder.
Data collection has stopped	Alarms and Events records are not being written to the active Event Chronicle database.
Data collection stopped	Real-time collection of historical data has stopped. Note This message may indicate that there is a problem opening the historical database or that there is a shortage of disk space for the historical database.
Database Error - All processing stopped	The SQL server has reported a failed transaction error following an attempt by the Batch Historian to create an entry in the Batch Historian database and the Batch Historian has discontinued creating entries in the Batch Historian database. Note This message may indicate a fault condition in the Batch Manager or Batch Historian.
Database Error - Failure to write events to the database	One or more Alarms and Events records configured for Event Chronicle collection have not been written to the Event Chronicle database.
Database Error - Failure to write history data	One or more history tags configured for history collection by the Continuous Historian have not been written to historical data storage.
Database is not available	A problem with accessing the database server for the Event Chronicle database has been detected. The problem is preventing Alarms and Events records from being written to or read from the file for the active Event Chronicle.
Database Space - All processing stopped due to database full	The amount of free space in the folder allocated for Batch Historian database storage has fallen below 3%, and the Batch Historian has discontinued creating entries in the Batch Historian database. You can increase the maximum size of the Batch Historian database storage folder in DeltaV Explorer by navigating to the Output tab on the Batch Historian Properties dialog for this workstation, selecting a location in the Directory Path column, and clicking Modify.
Failed - unable to communicate with Zone zone_name	The local Inter-Zone Server cannot communicate with the zone_name zone over either the primary or secondary Inter-Zone Networks.
HART Server Not Responding	WIOC: Usually a startup situation. No communication with the wireless devices is possible.
Lost Radio Communication with 781 Remote Link	WIOC: Not communicating with the Smart Wireless Field Link.
Node not configured	Valid configuration information has not been downloaded for the node. Note This message occurs when the Dnld parameter in DeltaV Diagnostics reports 0 for the time and date of the last good download to the node.
Not Communicating - Cannot collect data_source data from node node_name	The Batch Historian cannot connect to the Batch Executive, Campaign Manager, or Event Chronicle originating from the node_name node.
Not Communicating - on any Zone Network	The local Inter-Zone Server cannot communicate with any remote zone over either the primary or secondary Inter-Zone Networks.
Not Communicating - to Remote Node ID	The controller cannot establish communications with the remote I/O node.
Not Communicating - to Remote Node node_name	The controller cannot establish communications with the node_name remote I/O node.
Not Communicating - to Servernn	Communications with Servernn, an External Asset Server, cannot be established, preventing device alarms from this server.
Not Communicating - with, CIOC Name	The controller cannot communicate with the CHARM I/O card name (for example, CIOC-2)
Not Communicating - with Node Id: CIOC ID	The controller cannot communicate with the Node Id: CHARM I/O card ID (for example, 2517893127)
Unavailable - Zone zone_name alarm status	The local Inter-Zone Server cannot read the alarm status of the zone_name zone.
Connection Error - cannot connect to Zone zone_name	The local Inter-Zone Server has not been able to establish any communications with the configured zone_name zone since the last restart.
Server Error - Servernn reported an error	An error has been received from Servernn, an External Asset Server, preventing device alarms from this server. To review the text of the error, see the SvrErr parameter in DeltaV Diagnostics.
Server unavailable	One or more history tags is configured for history collection, but the Continuous Historian server is unavailable.
Service Failed to Start	The EventChronicleManager service that manages the SQL database server for the Event Chronicle database failed to start. Note If the EventChronicleManager service fails to start, this prevents low disk space warnings and the exporting or archiving of Alarms and Events records.
Unexpected Termination	The Batch Manager service has shut down unexpectedly.
Unexpected Campaign Manager Termination	The Campaign Manager service has shut down unexpectedly.