Knowledge Base

Warning

VMware vCenter Server Heartbeat 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 PrimarySrvA server while Passive. Further information if available: [N27]Failed to write information. See vCSHB-Ref-248 or VMware vCenter Server Heartbeat out of Disk Behavior (1008138).

Warning

VMware vCenter Server Heartbeat 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 SvrB while Passive. Further information if available: [N29]The passive VMware vCenter server attempted to access the file: E:\\DB\\TRAIN\\xz8. 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.

Warning

VMware vCenter Server Heartbeat Yellow Alert: Auto Switchover Started. This happened at Wed May 31 01:37:15 GMT+08:00 2006 on the PrimarySrvA server while Active. Further information if available: Auto switchover started because server lost connection to public 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.

Warning

VMware vCenter Server Heartbeat Yellow Alert: Failover complete. This happened at Mon Oct 30 15:27:15 GMT 2006 on the SecondarySrvB server while Active. For information regarding how to recover from a failover, see vCSHB-Ref-820 or Recovering from a failover (1008465).

Warning

VMware vCenter Server Heartbeat Yellow Alert: Heartbeat missed. This happened at Tue May 30 22:49:45 BST 2006 on the SecondarySvrBserver while Passive.

Warning

VMware vCenter Server Heartbeat Yellow Alert: Heartbeat stopped. This happened at Wed May 31 12:32:57 BST 2006 on the SecondarySvrB server while Passive. Further information if available:

Warning

VMware vCenter Server Heartbeat Yellow Alert: A VMware Channel has disconnected. This happened at Sat Jan 20 11:26:09 EST 2007 on the PrimarySvrA server while Active. If you regularly get this message please see vCSHB-Ref-992 or Troubleshooting a VMware Heartbeat Channel that drops (1008551).

Warning

VMware vCenter Server Heartbeat Yellow Alert: Failed to establish the VMware Channel. This happened at Sun Jan 21 14:31:18 CST 2007 on the SecondarySvrB server while Active. Further information if available: If you regularly get this error, see vCSHB-Ref-991 or Troubleshooting VMware vCenter Server Heartbeat Synchronization failures (1008572).

Warning

VMware vCenter Server Heartbeat 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 SecondarySvrB server while Passive. Further information if available: VMware vCenter Server Heartbeat has filled its quota with log files. Consider increasing the Max Disk Usage setting.

Warning

VMware vCenter Server Heartbeat 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, see vCSHB-Ref-240 or When Active Server fails, under certain situations, split-brain detections may prevent failover (1008137)and vCSHB-Ref-838 or Configuring Network Monitoring and Viewing the Network Status (1008467).

Information

VMware vCenter Server Heartbeat R2: VMware vCenter Server Heartbeat V5.5 (nnn) Has Shutdown Normally

Warning

VMware vCenter Server Heartbeat Red Alert: Timeout in application starting/stopping. This happened at Thu Jan 04 13:46:48 GMT 2007 on the SecondarySvrB server while Active. Further information if available: An application did not achieve its target status The application is :SQL ServerThe 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 VMware vCenter Server Heartbeat Console. - The script may not be issuing the relevant status commands: eg. <echo NFCMD doApplicationExecuting appName> eg. <echo NFCMD doApplicationStopped appName> - 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.

Warning

An attribute inbound Connections Current; Instance: Win32_PerfRawData_SMTPSVC_SMTPServer. Name="_Total" failed its check.

Warning

VMware vCenter Server Heartbeat Yellow Alert: Unprotected Feature Detected. This happened at Mon Apr 02 02:12:32 PDT 2007 on the Primary wasabi2 server while Active. Further information if available: Automated Out Of Synch Applied : Use ofunsupported featureshas been detected for the file / directory : D:\\Data\\ UNSUPPORTED2327518074\\As a result of this; the file / directoryis marked as Out Of Synch.