Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > ipMonitor > Orion Failover Engine installation log entries that may appear in the Application Event Log

Orion Failover Engine installation log entries that may appear in the Application Event Log

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 6 Votes: 0 Revisions: 9

Overview

This Knowledge Base article provides information about entries that may appear in the Application Event Log.

Environment

All Versions

Detail

 

 Event Name  Type  Example
 ApplyDiskFullEvent  Warning Orion Failover Engine Yellow Alert: Failed to update the Passive because the disk/Quota is full. This happened at Mon Feb 27 13:25:16 GMT 2006 on the Primary acme4 server while Passive. Further information if available: [N27]Failed to write information. Please see SWREFID - 1955.
 ApplySharingViolationEvent  Warning Orion Failover Engine Yellow Alert: Sharing violation on an object that was in use by another application. This happened at Wed Aug 02 23:11:36 BST 2006 on the Secondary ibsdb while Passive. Further information if available: [N29]The passive Orion Failover Engine server attempted to access the file: E:\\DB\\TRAIN\\ih.d1. This failed because the file was in use by another application. Please ensure that there are no applications which access protected files running on the passive.
 ControllerAutoSwitchoverEvent  Warning Orion Failover Engine Yellow Alert: Auto Switchover Started. This happened at Wed May 31 01:37:15 GMT+08:00 2006 on the Primary NFEX server while Active. Further information if available: Auto switchover started because server lost connection to principal network. The protected application will be started on the new  active server; but replication will be stopped. You must check the status of the protected application and its data before starting replication. When you start replication a full system check will be performed.
 ControllerFailoverDoneEvent  Warning Orion Failover Engine Yellow Alert: Failover complete. This happened at Mon Oct 30 15:27:15 GMT 2006 on the Secondary bosidex01 server while Active. For information regarding how to recover from a failover please see SWREFID - 1970.
 HeartbeatMissedEvent  Warning Orion Failover Engine Yellow Alert: Heartbeat missed. This happened at Tue May 30 22:49:45 BST 2006 on the Secondary gj1 server while Passive.
 HeartbeatStoppedEvent  Warning Orion Failover Engine Yellow Alert: Heartbeat stopped. This happened at Wed May 31 12:32:57 BST 2006 on the Secondary gj1 server while Passive. Further information if available:
 InvalidLicenseEvent  Warning Orion Failover Engine Red Alert: Invalid License. This happened at Fri Oct 13 20:42:33 EDT 2006 on the Primary atlas server while Active. Further information if available: No license keys are available which authorize Orion Failover Engine. License Hardware Id does not match this machine Please add a valid license key using the Configure Server Wizard. Please see SWREFID - 2007.
 NFChannelDisconnectedEvent  Warning Orion Failover Engine Yellow Alert: A SolarWinds Channel has disconnected. This happened at Sat Jan 20 11:26:09 EST 2007 on the Primary pia-ex1 server while Active. If you regularly get  this message please see SWREFID - 1929.
 NFChannelHandshakeFailedEvent  Warning Orion Failover Engine Yellow Alert: Failed to establish the SolarWinds Channel. This happened at Sun Jan 21 14:31:18 CST 2007 on the Secondary milex02 server while Active. Further information if available: Please see SWREFID - 2008 if you regularly get this error.
 NFChannelExceededMaxDisk
 UsageEvent
 
 Warning Orion Failover Engine Red Alert: Exceeded max disk space for queued file/registry update data. This happened at Sun Dec 24 06:58:37 GMT 2006 on the Secondary as47 server while Passive. Further information if available: Orion Failover Engine has filled its quota with log files. Consider increasing the Max Disk Usage setting.
 SplitBrainAvoidanceEvent  Warning Orion Failover Engine R2: Operation Failover failed because The channel connection has been lost; but the Active Server is still visible via the public network. Automatic failover has been prevented in order to avoid a split-brain (i.e. both servers active). For more information please see SWREFID - 1954 and SWREFID - 1977.
 ShutdownEvent  Information Orion Failover Engine R2: Orion Failover Engine (nnn) Has Shutdown Normally
 StatusTimeOutEvent  Warning Orion Failover Engine Red Alert: Timeout in application starting/stopping. This happened at Thu Jan 04 13:46:48 GMT 2007 on the Secondary exchsrv server while Active. Further information if available: An application did not achieve its target status The application is : Exchange The unachieved target status is : Executing Possible causes : - The application script or its timeout values may be set incorrectly: - Check the Application Configuration panel in the SolarWinds Orion Failover Manager. - The script may not be issuing the relevant status commands: e.g. <echo> eg. <echo/></echo> - The script may be running a command which is hanging: - If this happens when trying to stop an application; you should REBOOT your system. If a protected service refuses to stop; it will prevent data replication; so the system should not be used as a passive server without REBOOTING.
 An attribute failed its check (NF Monitor)  Warning  An attribute inbound Connections Current; Instance: Win32_PerfRawData_SMTPSVC_SMTPServer. Name="_Total" failed its check. For more information please see SWREFID - 2009.
 AlertableUnsupportedFeature
 UserEvent
Warning  Orion Failover Engine Yellow Alert: Unprotected Feature Detected. This happened at Mon Apr 02 02:12:32 PDT 2007 on the Primary was abi2 server while Active. Further information if available: Automated Out Of Synch Applied : Use of Extended Attributes / has been detected for the file / directory : D:\\Data\\ UNSUPPORTED2327518074\\ ExtAttrib\\ ExtAttribFolder As a result of this; the file / directory will be marked as Out Of Synch. For more information regarding this message please see SWREFID - 1957.

 

Last modified
19:36, 22 Jun 2016

Tags

Classifications

Public