Edit D:\Program Files (x86)\VMware\VMware Workstation\OVFTool\env\en\eventaux.vmsg

# en_US resources
signature="sIgNaTuRe"
###
###

HostInventoryFullEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostInventoryFullEvent">\
       <description>\
          The vCenter Server Foundation license key currently allows only three hosts to \
          be added to the inventory. Adding extra hosts results in errors \
          and the logging of this event. \
       </description>\
       <cause>\
            <description>Attempting to add more hosts than the number allowed by the license \
                         key assigned to vCenter Server</description>\
            <action>Assign vCenter Server a license key that allows more hosts or has \
                    no host limit</action>\
       </cause>\
    </EventLongDescription>\
    "

LicenseNonComplianceEvent.longDescription = "\
    <EventLongDescription id="vim.event.LicenseNonComplianceEvent">\
       <description>\
          vCenter Server does not strictly enforce license usage. Instead, it checks for license \
          overuse periodically. If vCenter Server detects overuse, it logs this event and \
	  triggers an alarm.\
       </description>\
       <cause>\
            <description>Overuse of licenses</description>\
            <action>Check the license reports through the vSphere Client and reduce the number of \
                    entities using the license key or add a new license key with a greater \
                    capacity</action>\
       </cause>\
    </EventLongDescription>\
    "

LicenseServerUnavailableEvent.longDescription = "\
    <EventLongDescription id="vim.event.LicenseServerUnavailableEvent">\
       <description>\
          vCenter Server tracks the license server state and logs this event if \
          the license server has stopped responding. \
       </description>\
       <cause>\
            <description>License server is not responding and not available to vCenter Server</description>\
            <action>Verify that the license server is running. If it is, check the connectivity between \
                    vCenter Server and the license server.</action>\
       </cause>\
    </EventLongDescription>\
    "

NoLicenseEvent.longDescription = "\
    <EventLongDescription id="vim.event.NoLicenseEvent">\
       <description>\
          vCenter Server logs this event if it fails to acquire a feature from the license server for an \
          unknown reason. \
       </description>\
       <cause>\
            <description>Acquiring a feature license fails for an unknown reason</description>\
            <action>Verify that the license server has the license for the feature</action>\
       </cause>\
    </EventLongDescription>\
    "

InvalidEditionEvent.longDescription = "\
    <EventLongDescription id="vim.event.InvalidEditionEvent">\
       <description>\
          vCenter Server attempted to acquire an undefined feature from the license server \
       </description>\
       <cause>\
            <description>Any operation that requires a feature license such as vMotion, DRS, vSphere HA might result \
                         in this event if that feature is not defined on the license server</description>\
            <action>Verify that the feature in question is present on the license server</action>\
       </cause>\
    </EventLongDescription>\
    "

HostLicenseExpiredEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostLicenseExpiredEvent">\
       <description>\
          vCenter Server tracks the expiration times of host licenses on the license server \
          and uses this event to notify you of any host licenses that are about to expire\
       </description>\
       <cause>\
            <description>Host licenses on the license server are about to expire</description>\
            <action>Update the license server to get a new version of the host license</action>\
       </cause>\
    </EventLongDescription>\
    "

VMotionLicenseExpiredEvent.longDescription = "\
    <EventLongDescription id="vim.event.VMotionLicenseExpiredEvent">\
       <description>\
          vCenter Server tracks the expiration times of vMotion licenses on the license server \
          and uses this event to notify you of any vMotion licenses that are about to expire\
       </description>\
       <cause>\
            <description>vMotion licenses on the license server are about to expire</description>\
            <action>Update the license server to get a fresher version of the vMotion license</action>\
       </cause>\
    </EventLongDescription>\
    "

LicenseRestrictedEvent.longDescription = "\
    <EventLongDescription id="vim.event.LicenseRestrictedEvent">\
       <description>\
          vCenter Server logs this event if it is unable to check out a license from the \
          license server due to restrictions in the license file \
       </description>\
       <cause>\
            <description>License file in the license server has restrictions that prevent check out</description>\
            <action>Check the license file and remove any restrictions that you can</action>\
       </cause>\
    </EventLongDescription>\
    "

VmFailedToPowerOffEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmFailedToPowerOffEvent">\
      <description>The virtual machine failed to power off</description>\
      <cause>\
         <description>\
            The virtual machine might be performing concurrent operations\
         </description>\
         <action>Complete the concurrent operations and retry the power-off operation</action>\
      </cause>\
      <cause>\
         <description>The virtual machine is in an invalid state. Virtual machines can enter an \
	    invalid state for many reasons, for example datastore inaccessibility. </description>\
         <action>\
            Identify the reason that the virtual machine entered an invalid state, correct the problem, \
	    and retry the operation.\
         </action>\
      </cause>\
   </EventLongDescription>\
   "

VmFailedToPowerOnEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmFailedToPowerOnEvent">\
      <description>\
         The virtual machine failed to power on\
      </description>\
      <cause>\
         <description>\
            Virtual machine power-on attempts can fail because the virtual machine is already in a \
            powered-on state, concurrent operations are running on the virtual machine, and so on. </description>\
         <action>\
	  Check the reason in the event message to find the cause of the power-on failure and fix the problem.\
         </action>\
      </cause>\
   </EventLongDescription>\
   "

VmFailedToRebootGuestEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmFailedToRebootGuestEvent">\
      <description>\
         The guest operating system on the virtual machine failed to reboot.\
      </description>\
      <cause>\
         <description>\
            Guest operating system reboot failures can occur because the virtual machine is not in a \
	    powered-on state, concurrent operations are running on the virtual machine, and so on.\
         </description>\
	 <action>\
	  Check the reason in the event message to find the cause of the reboot failure and fix the problem.\
         </action>\
       </cause>\
   </EventLongDescription>\
   "

VmFailedToResetEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmFailedToResetEvent">\
      <description>The virtual machine failed to reset</description>\
      <cause>\
         <description>\
		The virtual machine might be waiting for a response to a question or prompt</description>\
         <action>\
            Go to the Summary tab for the virtual machine in vSphere client and respond to the question \
	    or prompt\
         </action>\
      </cause>\
      <cause>\
         <description>There might not be enough available licenses to perform this operation.</description>\
         <action>\
            Obtain the required licenses and retry the reset operation\
         </action>\
      </cause>\
      <cause>\
         <description>\
            Concurrent operations might be executing on the virtual machine\
         </description>\
         <action>Complete the concurrent operations and retry the reset operation</action>\
      </cause>\
      <cause>\
         <description>\
            The host on which the virtual machine is running is entering maintenance mode\
         </description>\
         <action>\
            Wait until the host exits maintenance mode and retry the operation\
         </action>\
      </cause>\
      <cause>\
         <description>The virtual machine is in an invalid state. Virtual machines can enter an \
	    invalid state for many reasons, for example datastore inaccessibility.</description>\
         <action>\
            Identify the reason that the virtual machine entered an invalid state, correct the problem, \
	    and retry the operation.\
         </action>\
      </cause>\
   </EventLongDescription>\
   "

VmUpgradingEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmUpgradingEvent">\
      <description>The virtual hardware on this virtual machine is being upgraded</description>\
      <cause>\
         <description>A user-initiated action triggered an upgrade of the virtual machine hardware</description>\
      </cause>\
      <cause>\
         <description>A scheduled task started an upgrade of the virtual machine hardware</description>\
      </cause>\
   </EventLongDescription>\
   "

VmUuidAssignedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmUuidAssignedEvent">\
      <description>The virtual machine was assigned a new BIOS UUID</description>\
      <cause>\
         <description>The user who created the virtual machine did not specify a BIOS UUID at creation time. \
            vCenter Server generated a new UUID and assigned it to the virtual machine.\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmInstanceUuidAssignedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmInstanceUuidAssignedEvent">\
      <description>The virtual machine was assigned a new vCenter Server-specific instance UUID\
      </description>\
      <cause>\
         <description> \
             The user who created the virtual machine did not specify a vCenter Server-specific instance \
             UUID at creation time. vCenter Server generated a new UUID and assigned it to the \
	     virtual machine.\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmUuidChangedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmUuidChangedEvent">\
      <description>The virtual machine BIOS UUID has changed</description>\
      <cause>\
         <description>\
            A user changed the virtual machine BIOS UUID directly on the host\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmInstanceUuidChangedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmInstanceUuidChangedEvent">\
      <description> \
         The vCenter Server-specific instance UUID of the virtual machine has changed\
      </description> \
      <cause>\
         <description>\
            A user action resulted in a change to the vCenter Server-specific instance UUID of \
            the virtual machine\
         </description>\
      </cause>\
      <cause>\
         <description>\
            vCenter Server changed the instance UUID of the virtual machine because it detected \
            a conflict\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmInstanceUuidConflictEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmInstanceUuidChangedEvent">\
      <description> \
         The vCenter Server-specific instance UUID of the virtual machine conflicted with that of \
         another virtual machine. \
      </description>\
      <cause>\
         <description>\
             Virtual machine instance UUID conflicts can occur if you copy virtual machine files \
             manually without using vCenter Server. \
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmRelocateFailedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmRelocateFailedEvent">\
      <description>\
         Virtual machine relocation to a different host or datastore failed\
      </description>\
      <cause>\
         <description>\
            Virtual machine relocation can fail for a number of reasons, including \
            network outages, insufficient disk space, and so on\
         </description>\
         <action>\
            Consider the task related to this event, evaluate the failure reason, and take action accordingly\
         </action>\
      </cause>\
   </EventLongDescription>\
   "

VmUnsupportedStartingEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmUnsupportedStartingEvent">\
      <description>\
         Attempting to power on a virtual machine that has an unsupported guest operating system\
      </description>\
      <cause>\
         <description>\
            A user action initiated a virtual machine power-on operation, but the virtual machine has \
	    an unsupported guest operating system.\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

# VmRegisteredEvent: Basic event has enough details
# VmRenamedEvent: Basic event has enough details
# VmUuidConflictEvent: Not used anymore

VmFailedToShutdownGuestEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmFailedToShutdownGuestEvent">\
      <description>\
         Guest operating system shutdown failed for the virtual machine\
      </description>\
      <cause>\
         <description>\
            Guest operating system shutdown can fail if VMware Tools \
            is not installed in the virtual machine.\
         </description>\
         <action>Install VMware Tools.</action>\
      </cause>\
      <cause>\
         <description>\
	    The virtual machine might be waiting for a response to a question or prompt</description>\
         <action>\
            Go to the Summary tab for the virtual machine in vSphere Client and respond to the question \
	    or prompt\
         </action>\
      </cause>\
      <cause>\
         <description>\
            Concurrent operations might be running on the virtual machine\
         </description>\
         <action>Complete the concurrent operations and retry the shutdown operation</action>\
      </cause>\
      <cause>\
         <description>The virtual machine is in an invalid state. Virtual machines can enter an \
	    invalid state for many reasons, for example datastore inaccessibility.</description>\
         <action>\
            Identify the reason that the virtual machine entered an invalid state, correct the problem, \
	    and retry the operation.\
         </action>\
      </cause>\
   </EventLongDescription>\
   "

AlarmEmailFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.AlarmEmailFailedEvent">\
       <description>\
          An error occurred while sending email notification of a triggered alarm\
       </description>\
       <cause>\
            <description>Failed to send email for a triggered alarm</description>\
            <action>Check the vCenter Server SMTP settings for sending email notifications</action>\
       </cause>\
    </EventLongDescription>\
    "
    
AlarmReconfiguredEvent.longDescription = "\
    <EventLongDescription id="vim.event.AlarmReconfiguredEvent">\
       <description>\
          An alarm has been reconfigured \
       </description>\
       <cause>\
            <description>A user has reconfigured an alarm</description>\
       </cause>\
    </EventLongDescription>\
    "
        
AlarmScriptFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.AlarmScriptFailedEvent">\
       <description>\
          The vCenter Server logs this event if an error occurs while running a script after an alarm triggers.\
       </description>\
       <cause>\
            <description>There was an error running the script</description>\
            <action>Fix the script or failure condition</action>\
       </cause>\
    </EventLongDescription>\
    "

AlarmSnmpFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.AlarmSnmpFailedEvent">\
       <description>\
          The vCenter Server logs this event if an error occurs while sending an SNMP trap when an alarm triggers.\
       </description>\
       <cause>\
            <description>An SNMP trap could not be sent for a triggered alarm</description>\
            <action>Check the vCenter Server SNMP settings. Make sure that the vCenter Server network can handle SNMP packets.</action>\
       </cause>\
    </EventLongDescription>\
    "
   
   
ScheduledTaskEmailFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.ScheduledTaskEmailFailedEvent">\
       <description>\
          An error occurred while sending email notification that a scheduled task is running\
       </description>\
       <cause>\
            <description>Failed to send email for the scheduled task</description>\
            <action>Check the vCenter Server SMTP settings for sending emails</action>\
       </cause>\
    </EventLongDescription>\
    "

ScheduledTaskFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.ScheduledTaskFailedEvent">\
       <description>\
          An error occurred while running a scheduled task \
       </description>\
       <cause>\
            <description>Failed to run a scheduled task</description>\
            <action>Correct the failure condition</action>\
       </cause>\
    </EventLongDescription>\
    "

DasAgentUnavailableEvent.longDescription = "\
    <EventLongDescription id="vim.event.DasAgentUnavailableEvent">\
       <description>\
          vCenter Server is not able to contact any good primary hosts in the vSphere HA cluster. \
          vSphere HA protection may not be available for virtual machines running in the cluster. \
          In addition, you cannot enable or reconfigure vSphere HA on hosts in the \
          cluster until contact between vCenter Server and a good primary host is restored.\
       </description>\
       <cause>\
          <description>\
             There was a network outage, and all hosts show up in the inventory as "not responding"\
          </description>\
          <action>Restore the network</action>\
       </cause>\
       <cause>\
          <description>All the primary hosts in the cluster failed</description>\
          <action>\
             If the failed primary hosts cannot be restored, disable vSphere HA on the cluster, \
             wait for the Unconfigure vSphere HA tasks to complete on all hosts, and \
             re-enable vSphere HA on the cluster\
          </action>\
       </cause>\
    </EventLongDescription>\
    "

DasDisabledEvent.longDescription = "\
    <EventLongDescription id="vim.event.DasDisabledEvent">\
       <description>\
          vSphere HA has been disabled on this host due to a user action. vSphere HA is disabled when a host \
          is disconnected from vCenter Server or placed into maintenance or standby mode. \
          Virtual machines on other hosts in the cluster will not be failed over \
          to this host in the event of a host failure. In addition, if the host is disconnected, \
          any virtual machines running on this host will not be failed if the host fails. Further, \
          no attempt will be made by vSphere HA VM and Application Monitoring to reset VMs. \
       </description>\
    </EventLongDescription>\
    "

DasEnabledEvent.longDescription = "\
    <EventLongDescription id="vim.event.DasEnabledEvent">\
       <description>\
          vSphere HA has been enabled on this host due to a user action. vSphere HA is enabled when a host \
          is added to or moved into an vSphere HA cluster or when vSphere HA is enabled on a cluster. If the host \
          was already in an vSphere HA cluster, vSphere HA will be enabled when the host is reconnected to vCenter \
          Server or brought out of maintenance or standby mode. vSphere HA will attempt to protect any VMs that are \
          running on the host at the time that HA is enabled on it. \
       </description>\
    </EventLongDescription>\
    "

HostDasEnablingEvent.longDescription = "\
     <EventLongDescription id="vim.event.HostDasEnablingEvent">\
        <description>\
           vSphere HA is being enabled on this host.\
        </description>\
     </EventLongDescription>\
     "

InsufficientFailoverResourcesEvent.longDescription = "\
     <EventLongDescription id="vim.event.InsufficientFailoverResourcesEvent">\
        <description>\
            The cluster does not have enough unreserved capacity to satisfy the level configured \
            for vSphere HA admission control. Failovers may still be performed by vSphere HA but will be on a \
            best effort basis.\
        </description>\
        <cause>\
            <description>\
                If the "number of host failures to tolerate" policy is configured and a few \
                virtual machines have a much higher CPU or memory reservation than the other \
                virtual machines, vSphere HA admission control can be excessively conservative \
                to ensure that there are enough unfragmented resources if a host fails.\
            </description>\
            <action>\
                Use similar CPU and memory reservations for all virtual machines \
                in the cluster. If this is not possible, consider using a different vSphere HA admission \
                control policy, such as reserving a percentage of cluster resource for failover. \
                Alternatively, you can use advanced options to specify a cap for the slot size. \
                See the vSphere Availability Guide for details.\
            </action>\
        </cause>\
        <cause>\
           <description>\
                Hosts with vSphere HA agent errors are not good candidates \
                for providing failover capacity in the cluster, and their resources are \
                not considered for vSphere HA admission control purposes. If many hosts have an \
                vSphere HA agent error, vCenter Server generates this event.\
           </description>\
           <action>\
                Check the event log of the hosts to determine the cause of the vSphere HA agent errors. \
                After addressing any configuration issues, reconfigure vSphere HA on the affected \
                hosts or on the cluster.\
           </action>\
        </cause>\
     </EventLongDescription>\
     "

VmDasBeingResetEvent.longDescription = "\
     <EventLongDescription id="vim.event.VmDasBeingResetEvent">\
        <description>\
           The virtual machine was reset by vSphere HA. Depending on how vSphere HA has been configured, \
           the virtual machine might be reset because the VMware Tools heartbeat or application \
           heartbeat status turned red.\
        </description>\
        <cause>\
           <description>\
                The VMware Tools heartbeat turned red. This condition can occur if the operating \
                system failed with a blue screen or becomes unresponsive. It also can occur because \
		VMware Tools failed or was shut down.\
           </description>\
           <action>\
                If the virtual machine is reset frequently, check for a \
                persistent problem with the operating system that requires attention. \
                Consider configuring the cluster so that vSphere HA waits for a longer period after \
                heartbeats are lost before taking action. Specifying a longer period helps avoid \
                triggering resets for transient problems. You can force a longer period by decreasing \
		the "monitoring sensitivity" in the VM Monitoring section of the Edit Cluster wizard.\
           </action>\
        </cause>\
        <cause>\
           <description>\
                The application heartbeat turned red. This condition can occur if the application \
                that is configured to send heartbeats failed or became unresponsive.\
           </description>\
           <action>\
                Determine if the application stopped sending heartbeats because of a configuration \
                error and remediate the problem.\
           </action>\
        </cause>\
     </EventLongDescription>\
     "

VmDasBeingResetWithScreenshotEvent.longDescription = "\
     <EventLongDescription id="vim.event.VmDasBeingResetWithScreenshotEvent">\
        <description>\
           The virtual machine was reset by vSphere HA. Depending on how vSphere HA is configured, \
           this condition can occur because the VMware Tools heartbeat or the application \
           heartbeat status turned red. The event contains the location of the screenshot \
           taken of the guest console before it was reset. You can use this information to determine\
           the cause of the heartbeat failure.\
        </description>\
        <cause>\
           <description>\
                The VMware Tools heartbeat turned red. This condition can occur if the operating \
                system failed with a blue screen or becomes unresponsive. It also can occur because \
		VMware Tools failed or was shut down.\
           </description>\
           <action>\
                Check the screenshot image to see if the cause was a guest operating system failure.\
                If the virtual machine is reset frequently, check for a \
                persistent problem with the operating system that requires attention. \
                Consider configuring the cluster so that vSphere HA waits for a longer period after \
                heartbeats are lost before taking action. Specifying a longer period helps avoid \
                triggering resets for transient problems. You can force a longer period by decreasing \
		the "monitoring sensitivity" in the VM Monitoring section of the Edit Cluster wizard.\
           </action>\
        </cause>\
        <cause>\
           <description>\
                The application heartbeat turned red. This condition can occur if the application \
                that is configured to send heartbeats failed or became unresponsive.\
           </description>\
           <action>\
                Determine if the application stopped sending heartbeats because of a configuration \
                error and remediate the problem.\
           </action>\
        </cause>\
     </EventLongDescription>\
     "

VmDasResetFailedEvent.longDescription = "\
     <EventLongDescription id="vim.event.VmDasResetFailedEvent">\
        <description>\
            vSphere HA attempted to reset the virtual machine because of a heartbeat failure \
            from VMware Tools or a guest application, depending on how vSphere HA was \
            configured. However, the reset operation failed.\
        </description>\
        <cause>\
            <description>\
                The most likely reason for the reset failure is that the virtual machine was running \
                another task at the time the reset was initiated.\
            </description>\
            <action>Check to see whether the virtual machine requires attention and reset \
                it manually if necessary.</action>\
        </cause>\
     </EventLongDescription>\
     "

VmFailoverFailed.longDescription = "\
     <EventLongDescription id="vim.event.VmFailoverFailed">\
        <description>\
           vSphere HA did not failover this virtual machine. The event includes the details of the fault that \
           was generated when vSphere HA attempted the failover. vSphere HA will retry the failover on another \
           host unless the maximum number of failover attempts have been exceeded. In many cases, the retry \
           will succeeed.\
        </description>\
        <cause>\
           <description>\
                The failover did not succeed because a problem occurred while vSphere HA was trying to restart \
                the virtual machine. Possible problems include the inability to register or reconfigure the virtual\
                machine on the new host because another operation on the same virtual machine is\
                already in progress, or because the virtual machine is still powered on. It may also occur if the \
                configuration file of the virtual machine is corrupt.\
           </description>\
           <action> \
                   If vSphere HA is unable to failover the virtual machine after repeated attempts, investigate the \
                   error reported by each occurences of this event, or trying powering on the virtual \
                   machine and investigate any returned errors.\
           </action> \
           <action> \
                   If the error reports that a \
                   file is locked, the VM may be powered on a host that the vSphere HA master agent can no longer \
                   monitor using the management network or heartbeat datastores, or it may have been powered on by a \
                   user on a host outside of the cluster. If any hosts have been declared dead, investigate whether a \
                   networking/storage issue may be the cause. \
           </action> \
           <action> \
                   If, however, the error reports that the virtual machine is \
                   in an invalid state, there may be an inprogress operation that is preventing access to the \
                   virtual machine's files. Investigate whether there are in-progress operations, such as a clone operation \
                   that is taking a long time to complete. \
           </action>\
        </cause>\
     </EventLongDescription>\
     "

VmMaxRestartCountReached.longDescription = "\
     <EventLongDescription id="vim.event.VmMaxRestartCountReached">\
        <description>\
           vSphere HA has reached the maximum number of failover attempts for this virtual \
           machine and has not been able to restart it. No further failover attempts \
           will be made. By default vSphere HA attempts to failover a virtual machine 5 times. \
        </description>\
        <cause>\
           <description>\
                Failover can fail for a number of reasons including that  \
                the configuration file of the virtual machine is corrupt or one or more of the virtual \
                machines datastores are not accessible by any host in the cluster due to an all paths\
                down condition. In addition, the VM may be powered on a host that the vSphere HA master agent \
                can no longer monitor using the management network or heartbeat datastores, or it may have been \
                powered on by a user on a host outside of the cluster. \
           </description>\
           <action>\
                To determine why previous failover attempts failed, search the events that are logged \
                for the VM for occurences of the event vSphere HA reports when a failover fails. These events \
                will report the reason for the failed failover. vSphere HA events can be located by searching \
                for the phrase 'vSphere HA'. To determine whether any issues still exist, try \
                to manually power on the virtual machine. If power-on fails, investigate the error \
                that is returned. But, if the power-on remains pending for a long time, \
                investigate whether an all paths down condition exists. Also, if any hosts have been declared dead,\
                investigate whether a networking or storage issue may be the cause. \
           </action>\
        </cause>\
     </EventLongDescription>\
     "

VmPowerOffOnIsolationEvent.longDescription = "\
     <EventLongDescription id="vim.event.VmPowerOffOnIsolationEvent">\
        <description>\
           vSphere HA powered off this virtual machine because the host it was running on \
           was isolated from the management network. \
        </description>\
     </EventLongDescription>\
     "

VmShutdownOnIsolationEvent.longDescription = "\
     <EventLongDescription id="vim.event.VmShutdownOnIsolationEvent">\
        <description>\
           vSphere HA shut down this virtual machine because the host it was running on \
           was isolated from the management network.\
        </description>\
     </EventLongDescription>\
     "

VmAutoRenameEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmAutoRenameEvent">\
       <description>\
          The virtual machine was renamed because of possible name conflicts with another virtual machine\
       </description>\
       <cause>\
            <description>The virtual machine might have been added to the vCenter Server inventory while \
               scanning the datastores of hosts added to the inventory. During such an action, the \
	       newly-added virtual machine's name might have been found to be in conflict with a virtual \
               machine name already in the inventory. To resolve this, vCenter Server renames the \
	       newly-added virtual machine.\
            </description>\
        </cause>\
    </EventLongDescription>\
    "

VmBeingDeployedEvent.longDescription = "\
     <EventLongDescription id="vim.event.VmBeingDeployedEvent">\
        <description>\
           A virtual machine is being created from a template\
        </description>\
        <cause>\
             <description>\
                A user action prompted a virtual machine to be created from this template.\
             </description>\
         </cause>\
     </EventLongDescription>\
     "

VmBeingHotMigratedEvent.longDescription = "\
  <EventLongDescription id="vim.event.VmBeingHotMigratedEvent">\
     <description>\
        A powered-on virtual machine is being migrated with vMotion\
     </description>\
     <cause>\
          <description> A user action might have caused a powered-on virtual machine to be migrated with vMotion\
          </description>\
      </cause>\
       <cause>\
          <description> A DRS recommendation might have caused a powered-on virtual machine to be migrated \
	  with vMotion\
          </description>\
      </cause>\
  </EventLongDescription>\
  "

DatastoreDiscoveredEvent.longDescription = "\
  <EventLongDescription id="vim.event.DatastoreDiscoveredEvent">\
     <description>\
        A datastore was discovered on a host\
     </description>\
     <cause>\
        <description>\
           A host that has access to this datastore was added to the datacenter\
        </description>\
     </cause>\
     <cause>\
        <description>\
           The storage backing this datastore was unmasked to a host in the datacenter\
        </description>\
     </cause>\
     <cause>\
        <description>\
           A user or system action caused this datastore to be created on a host\
        </description>\
     </cause>\
     <cause>\
        <description>\
           A user or system action caused this datastore to be created on a host and \
           the datastore was visible on at least one other host in the datacenter prior to this \
           operation. \
        </description>\
     </cause>\
   </EventLongDescription>\
   "

DatastoreRenamedOnHostEvent.longDescription = "\
   <EventLongDescription id="vim.event.DatastoreRenamedOnHostEvent">\
      <description>\
         A datastore was renamed on a host managed by vCenter Server\
      </description>\
      <cause>\
         <description>\
            vCenter Server discovered datastore on a host and renamed the datastore \
            because it already exists in the vCenter Server inventory under a different name. \
            vCenter Server might also have renamed the datastore because the name conflicts with \
	    another datastore in the same datacenter. \
         </description>\
      </cause>\
   </EventLongDescription>\
  "

VMFSDatastoreExtendedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VMFSDatastoreExtendedEvent">\
      <description>\
         An existing VMFS volume was extended to increase its capacity\
      </description>\
      <cause>\
         <description>\
            A user or system action caused the datastore to be extended with a partition \
            on a LUN to increase its capacity. \
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VMFSDatastoreExpandedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VMFSDatastoreExpandedEvent">\
      <description>\
         An existing extent in a VMFS volume was grown to increase its capacity\
      </description>\
      <cause>\
         <description>\
            A user or system action caused an extent of an existing VMFS datastore  \
            to be grown. Only extents with free space immediately after them \
            are expandable. As a result, the action filled the available  \
            adjacent capacity on the LUN.\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmConfigMissingEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmConfigMissingEvent">\
      <description>\
         One or more configuration files for the virtual machine cannot be found\
      </description>\
      <cause>\
         <description>\
            The datastore on which this virtual machine resides may be inaccessible\
         </description>\
         <action>\
             Check the connectivity of the datastore on which this virtual machine \
             resides. If the datastore has a backing LUN, check to see if there are \
             any transient disk failures.\
         </action>\
      </cause>\
   </EventLongDescription>\
   "

VmDeployedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmDeployedEvent">\
      <description>\
         A virtual machine has been created from the specified template\
      </description>\
      <cause>\
         <description>\
            A user action caused a virtual machine to be created from the template\
         </description>\
      </cause>\
      <cause>\
         <description>\
            A scheduled task caused a virtual machine to be created from the template\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmMacChangedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmMacChangedEvent">\
      <description>\
         The virtual machine MAC address has changed\
      </description>\
      <cause>\
         <description>\
            A user action changed the virtual machine MAC address\
         </description>\
      </cause>\
      <cause>\
         <description>\
            vCenter changed the virtual machine MAC address because it detected \
            a MAC address conflict\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmMacConflictEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmMacConflictEvent">\
      <description>\
         The virtual machine MAC address conflicts with that of \
         another virtual machine\
      </description>\
      <cause>\
         <description> This virtual machine's MAC address is the same \
            as that of another virtual machine.\
            Refer to the event details for more information on the \
            virtual machine that caused the conflict.\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmOrphanedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmOrphanedEvent">\
      <description>\
         The virtual machine does not exist on the host with which it is associated\
      </description>\
      <cause>\
         <description> The virtual machine was deleted while its host was disconnected from vCenter Server. \
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmConnectedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmConnectedEvent">\
      <description>\
         The virtual machine is in a connected state in the inventory \
         and vCenter Server can access it\
      </description>\
      <cause>\
         <description>\
            A user or system action that resulted in operations such as creating, \
            registering, cloning or deploying a virtual machine gave vCenter Server access to \
            the virtual machine\
         </description>\
      </cause>\
       <cause>\
         <description>\
            A user or system action that resulted in operations such as adding or \
            reconnecting a host gave vCenter Server access to the virtual machine\
         </description>\
      </cause>\
      <cause>\
         <description>\
            The state of the virtual machine's host changed from \
            Not Responding to Connected and the host gave vCenter Server access to the virtual machine\
         </description>\
      </cause>\
    </EventLongDescription>\
    "
   MigrationErrorEvent.longDescription = "\
         <EventLongDescription id="vim.event.MigrationErrorEvent">\
            <description>\
               A virtual machine failed to migrate because it did not meet all compatibility criteria\
            </description>\
            <cause>\
                 <description> Migrating a virtual machine from the source host failed because \
                     the virtual machine did not meet all the compatibility criteria\
                 </description>\
                  <action> \
                      Use the VSphere Client to check for errors at the time \
                      of the failure so that you can identify possible reasons for this problem\
                  </action>\
             </cause>\
         </EventLongDescription>\
         "

MigrationHostErrorEvent.longDescription = "\
         <EventLongDescription id="vim.event.MigrationHostErrorEvent">\
            <description>\
               A virtual machine failed to migrate because it did not meet all compatibility criteria\
            </description>\
            <cause>\
                 <description> Migrating a virtual machine to the destination host or datastore failed \
                     because the virtual machine did not meet all the compatibility criteria\
                 </description>\
                  <action> \
                      Use the VSphere Client to check for errors at the time \
                      of the failure so that you can identify possible reasons for this problem\
                  </action>\
             </cause>\
         </EventLongDescription>\
         "

VmBeingMigratedEvent.longDescription = "\
     <EventLongDescription id="vim.event.VmBeingMigratedEvent">\
        <description>\
           Changing the host on which the virtual machine is executing\
        </description>\
        <cause>\
           <description>\
                A user action caused the virtual machine to be migrated to a different host\
           </description>\
        </cause>\
     </EventLongDescription>\
     "

VmMigratedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmMigratedEvent">\
      <description>\
         The virtual machine's host was changed successfully\
      </description>\
      <cause>\
         <description>\
            A user action caused the virtual machine \
            to be successfully migrated to a different host\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmBeingRelocatedEvent.longDescription = "\
     <EventLongDescription id="vim.event.VmBeingRelocatedEvent">\
        <description>\
           The virtual machine execution and/or storage is being relocated\
        </description>\
        <cause>\
           <description>\
                A user action might have caused the virtual machine's execution and/or storage to be changed\
           </description>\
        </cause>\
     </EventLongDescription>\
     "

VmRelocatedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmRelocatedEvent">\
      <description>\
         The virtual machine execution and/or storage was successfully relocated\
      </description>\
      <cause>\
         <description>\
            A user action caused the virtual machine's execution \
            and/or storage to be successfully changed\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmCloneFailedEvent.longDescription = "\
     <EventLongDescription id="vim.event.VmCloneFailedEvent">\
        <description>\
           Cloning a virtual machine failed\
        </description>\
        <cause>\
           <description>\
                An error prevented the virtual machine from being cloned\
           </description>\
        </cause>\
     </EventLongDescription>\
     "

MigrationHostWarningEvent.longDescription = "\
         <EventLongDescription id="vim.event.MigrationHostWarningEvent">\
            <description>\
               The virtual machine can be migrated but might lose some functionality after migration \
	       is complete\
            </description>\
            <cause>\
                 <description> Migrating the virtual machine to the destination host or datastore is likely to \
                     succeed but some functionality might not work correctly afterward because the virtual \
	    	     machine did not meet all the compatibility criteria.\
                 </description>\
                  <action> \
                      Use the VSphere Client to check for warnings at the time \
                      of the failure so that you can identify possible reasons for this problem\
                  </action>\
             </cause>\
         </EventLongDescription>\
         "

MigrationResourceErrorEvent.longDescription = "\
         <EventLongDescription id="vim.event.MigrationResourceErrorEvent">\
            <description>\
               A virtual machine failed to migrate due to incompatibilities with target resource pool\
            </description>\
            <cause>\
                 <description>Migrating a virtual machine to the destination host or datastore is not \
                 possible due to incompatibilities with the target resource pool.\
                 </description>\
                  <action> \
                      Use the VSphere Client to check for errors at the time \
                      of the failure so that you can identify possible reasons for this problem\
                  </action>\
             </cause>\
         </EventLongDescription>\
         "

MigrationResourceWarningEvent.longDescription = "\
         <EventLongDescription id="vim.event.MigrationResourceWarningEvent">\
            <description>\
               The virtual machine can be migrated but might lose some functionality after migration \
	       is complete\
            </description>\
            <cause>\
                 <description> Migrating the virtual machine to the destination resource pool is likely to \
                     succeed but some functionality might not work correctly afterward because the virtual \
	    	     machine did not meet all the compatibility criteria.\
                 </description>\
                  <action> \
                      Use the VSphere Client to check for warnings at the time \
                      of the failure so that you can identify possible reasons for this problem\
                  </action>\
             </cause>\
         </EventLongDescription>\
         "

VmDeployFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmDeployFailedEvent">\
        <description>\
           Failed to deploy a virtual machine for reasons described in the event message\
        </description>\
        <cause>\
           <description>\
                The virtual machine failed to deploy. \
                This condition can occur if there is not enough disk space, the host or virtual machine loses \
		its network connection, the host is disconnected, and so on.\
           </description>\
          <action>\
	    Check the reason in the event message to find the cause of the failure and correct the problem.\
         </action>\
	</cause>\
     </EventLongDescription>\
     "

VmDiskFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmDiskFailedEvent">\
        <description>\
           Failed to create a virtual disk for the virtual machine for reasons described in the event message\
        </description>\
        <cause>\
           <description>\
                A virtual disk was not created for the virtual machine. This condition can occur if the \
		operation failed to access the disk, the disk did not have enough space, you do not have \
		permission for the operation, and so on.\
           </description>\
           <action>\
                Check the reason in the event message to find the cause of the failure. Ensure that disk is \
		accessible, has enough space, and that the permission settings allow the operation.\
           </action>\
        </cause>\
     </EventLongDescription>\
     "

VmFailedMigrateEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmFailedMigrateEvent">\
        <description>\
           Failed to migrate the virtual machine for reasons described in the event message\
        </description>\
        <cause> \
            <description> \
                The virtual machine did not migrate. This condition can occur if vMotion IPs are not configured, \
                the source and destination hosts are not accessible, and so on.\
            </description> \
            <action> \
                Check the reason in the event message to find the cause of the failure. Ensure that the \
		vMotion IPs are configured on source and destination hosts, the hosts are accessible, and so on.\
            </action> \
        </cause> \
     </EventLongDescription>\
     "

VmFailedRelayoutOnVmfs2DatastoreEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmFailedRelayoutOnVmfs2DatastoreEvent">\
        <description>\
           Failed to migrate a virtual machine on VMFS2 datastore\
        </description>\
        <cause>\
           <description>\
                An attempt to migrate a virtual machine failed because the \
                virtual machine still has disk(s) on a VMFS2 datastore. VMFS2 datastores are read-only for \
                ESX 3.0 and later hosts.\
           </description>\
           <action> \
                Upgrade the datastore(s) from VMFS2 to VMFS3\
           </action> \
        </cause>\
     </EventLongDescription>\
     "

VmFailedRelayoutEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmFailedRelayoutEvent">\
        <description>\
           Failed to lay out a virtual machine \
        </description>\
        <cause>\
           <description>\
                An attempt to lay out a virtual machine on disk failed for reasons described in the event message. \
                This condition can occur for any of several reasons, for example inability to access the disk.\
           </description>\
        <action>\
	    Check the reason in the event message to find the cause of the failure and correct the problem.\
         </action>\
	</cause>\
     </EventLongDescription>\
     "

VmAcquiredMksTicketEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmAcquiredMksTicketEvent">\
        <description>\
           Successfully acquired MKS Ticket for the virtual machine\
        </description>\
        <cause>\
           <description>\
                The MKS Ticket used to connect to the virtual machine remote console \
                has been successfully acquired.\
           </description>\
        </cause>\
     </EventLongDescription>\
     "

VmWwnAssignedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmWwnAssignedEvent">\
      <description>\
         The virtual machine was assigned a WWN (World Wide Name)\
      </description>\
      <cause>\
         <description>The virtual machine was assigned a WWN because it \
            was created with an RDM (Raw Device Mappings) disk or was \
            reconfigured to access an RDM disk\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmWwnChangedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmWwnChangedEvent">\
      <description>\
         The WWN (World Wide Name) assigned to the virtual machine was changed \
      </description>\
      <cause>\
         <description>The virtual machine was assigned a new WWN, possibly due \
         to a conflict caused by another virtual machine being \
         assigned the same WWN\
         </description>\
      </cause>\
   </EventLongDescription>\
   "

VmWwnConflictEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmWwnConflictEvent">\
      <description>\
         The WWN (World Wide Name) assigned to the virtual machine has a \
         conflict \
      </description>\
      <cause>\
         <description>The WWN assigned to this virtual machine was the same \
            as that of a different virtual machine.\
       </description>\
      <action>\
	    Check the event details for more information on the conflict and correct the problem.\
         </action>\</cause>\
   </EventLongDescription>\
   "

VmReloadFromPathFailedEvent.longDescription = "\
   <EventLongDescription id="vim.event.VmReloadFromPathFailedEvent">\
      <description>\
         Reloading the virtual machine from a new datastore path failed \
      </description>\
      <cause>\
         <description>The destination datastore path was inaccessible or \
         invalid\
         </description>\
         <action>Use a valid destination datastore path \
         </action> \
      </cause>\
      <cause>\
         <description>The virtual machine is in an invalid state \
         </description>\
         <action>Check the virtual machine state power state. If the virtual machine is \
            powered on, power it off \
         </action>\
      </cause>\
      <cause>\
         <description>The virtual machine is enabled for Fault Tolerance\
         </description>\
         <action>Disable Fault Tolerance for the virtual \
            machine and retry the operation \
         </action>\
      </cause>\
   </EventLongDescription>\
   "

CustomizationLinuxIdentityFailed.longDescription = "\
   <EventLongDescription id="vim.event.CustomizationLinuxIdentityFailed">\
      <description>\
         The guest operating system Linux distribution is not supported by the customization scripts. \
         Please refer to the VMware vSphere Compatibility Matrix for the list of the supported Linux \
         distributions.\
      </description>\
      <cause>\
         <description>\
            Customization of the target guest operating system Linux distribution is not supported.\
         </description>\
         <action>\
            Consult with VMware on when the specific Linux distribution will \
            be supported. If the Linux distribution is already supported in a newer release, consider upgrading.\
         </action>\
      </cause>\
   </EventLongDescription>\
   "

CustomizationNetworkSetupFailed.longDescription = "\
   <EventLongDescription id="vim.event.CustomizationNetworkSetupFailed">\
      <description>\
         The customization scripts failed to set the parameters \
         in the corresponding configuration files for Linux or in the \
         Windows registry\
      </description>\
      <cause>\
         <description>\
            The Customization Specification contains an invalid host name or domain name\
         </description>\
         <action>\
            Review the guest operating system log files for this event for more details\
         </action>\
         <action>\
            Provide a valid host name for the target guest operating system. The name must comply \
            with the host name and domain name definitions in RFC 952, 1035, 1123, 2181.\
         </action>\
      </cause>\
      <cause>\
         <description>\
            Could not find a NIC with the MAC address specified in the Customization Package \
         </description>\
         <action>\
            Review the guest operating system log files for this event for more details\
         </action>\
         <action>\
            Confirm that there was no change in the virtual NIC MAC address between \
            the creation of the Customization Package and its deployment. Deployment occurs \
            during the first boot of the virtual machine after customization has been scheduled.\
         </action>\
      </cause>\
      <cause>\
         <description>\
            The customization code needs read/write permissions for certain configuration files. \
	    These permissions were not granted to the 'root' account on Linux \
            or to the account used by the VMware Tools Service on the Windows guest operating system.\
         </description>\
         <action>\
            Review the guest operating system log files for this event for more details\
         </action>\
         <action>\
            Grant read/write permissions to the 'root' account for Linux or to the \
            account used by the VMware Tools Service on the Windows guest operating system \
            and the registry keys that need to be modified by the customization code\
         </action>\
      </cause>\
   </EventLongDescription>\
   "

CustomizationSysprepFailed.longDescription = "\
   <EventLongDescription id="vim.event.CustomizationSysprepFailed">\
      <description>\
         The sysprep files in the folder corresponding to the \
         selected target guest operating system are not compatible with the \
         actual version of the guest operation system\
      </description>\
      <cause>\
         <description>\
            The sysprep files in the folder corresponding to the target guest operating system \
	    (for example Windows XP) are for a different guest operating system (for example Windows 2003)\
         </description>\
         <action>\
            On the machine running vCenter Server, place the correct sysprep files in the folder \
	    corresponding to the target guest operating system\
         </action>\
      </cause>\
      <cause>\
         <description>\
            The sysprep files in the folder corresponding to the guest operating system are for a \
            different Service Pack, for example the guest operating system is Windows XP SP2 and but the \
            sysprep files are for Windows XP SP1.\
         </description>\
         <action>\
            On the machine running vCenter Server, place the correct sysprep files in the folder \
	    corresponding to the target guest operating system\
         </action>\
      </cause>\
   </EventLongDescription>\
   "

CustomizationUnknownFailure.longDescription = "\
   <EventLongDescription id="vim.event.CustomizationUnknownFailure">\
      <description>\
         The customization component failed to set the required parameters \
         inside the guest operating system\
      </description>\
      <cause>\
         <description>\
            On Windows, the user account under which the customization code runs has no \
	    read/write permissions for the registry keys used by the customization code. \
	    Customization code is usually \
            run under the 'Local System' account but you can change this by \
            selecting a different account for VMware Tools Service execution.\
         </description>\
         <action>\
            Review the guest operating system log files for this event for more details\
         </action>\
         <action>\
            Determine which user account is selected for VMware Tools Service execution and \
            confirm that this account has read/write permissions on registry keys \
            used by the customization code\
         </action>\
      </cause>\
      <cause>\
         <description>\
            On Windows, the user account under which the customization code runs has no read/write \
	    permissions for the files and folders used by the customization code. \
            Customization code is usually run \
            under the 'Local System' account but you can change this by selecting a \
            different account for VMware Tools Service execution.\
         </description>\
         <action>\
            Review the guest operating system log files for this event for more details\
         </action>\
         <action>\
            Determine which user account is selected for VMware Tools Service execution and \
            confirm that this account has read/write permissions on the files and folders \
            used by the customization code\
         </action>\
      </cause>\
      <cause>\
         <description>\
            On Linux, an invalid or unsupported time zone is passed to the customization \
            scripts and the time zone configuration failed as a result\
         </description>\
         <action>\
            Review the guest operating system log files for this event for more details\
         </action>\
         <action>\
            Confirm that a supported time zone is passed in Customization Specification.\
         </action>\
      </cause>\
      <cause>\
         <description>\
            On Linux, the guest operating system 'root' account does not have read/write \
	    permissions for the configuration files that the customization scripts need to modify \
	    ('/etc/hosts')\
         </description>\
         <action>\
            Grant read/write permissions for the configuration files to the guest operating system 'root' \
	    account\
         </action>\
      </cause>\
      <cause>\
         <description>\
            To enable guest customization on Linux, in case open-vm-tools are used, you must also install the  \
            deployPkg plug-in.\
         </description>\
         <action>\
            Follow kb.vmware.com/kb/2075048 to install the open-vm-tools deployPkg plug-in.\
         </action>\
      </cause>\
      <cause>\
         <description>\
            Customization of the target guest operating system is not supported\
         </description>\
         <action>\
            Consult with VMware on when the specific Linux distribution will \
            be supported. If the Linux distribution is already supported in a newer release, consider upgrading.\
         </action>\
      </cause>\
   </EventLongDescription>\
   "
#
# FT Related Events
#

VmFailedStartingSecondaryEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmFailedStartingSecondaryEvent">\
       <description>\
          vCenter Server could not start the Secondary VM because of an error\
       </description>\
       <cause>\
            <description>\
              The remote host is incompatible for Secondary VM. \
              For instance, this condition can occur when the host does not have access to the \
              virtual machine's network or datastore.\
            </description>\
            <action>Ensure that the hosts in the cluster are compatible for FT</action>\
        </cause>\
        <cause>\
            <description>Login to a remote host failed. If the host has been newly added to the inventory \
		or just rebooted, it might take some time for SSL thumbprints to be propagated to the hosts.\
            </description>\
            <action>If the problem persists, disconnect and re-connect the host.</action>\
        </cause>\
        <cause>\
            <description>Registration of the Secondary VM on the remote host failed</description>\
            <action>Determine whether the remote host has access to the datastore that the FT \
		virtual machine resides on</action>\
        </cause>\
        <cause>\
            <description>An error occurred while starting the Secondary VM</description>\
            <action>Determine the cause of the migration error. vCenter Server will try to restart the \
		Secondary VM if it can.</action>\
        </cause>\
    </EventLongDescription>\
    "

VmFailedUpdatingSecondaryConfig.longDescription = "\
    <EventLongDescription id="vim.event.VmFailedUpdatingSecondaryConfig">\
       <description>\
          After a failover, the new Primary VM failed to update the configuration of the Secondary VM\
       </description>\
       <cause>\
            <description> </description>\
            <action></action>\
        </cause>\
    </EventLongDescription>\
    "

VmFaultToleranceStateChangedEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmFaultToleranceStateChangedEvent">\
       <description>\
          The Fault Tolerance state of the virtual machine changed\
       </description>\
       <cause>\
            <description> </description>\
            <action></action>\
        </cause>\
    </EventLongDescription>\
    "

VmFaultToleranceTurnedOffEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmFaultToleranceTurnedOffEvent">\
       <description>\
          All Secondary VMs have been removed and Fault Tolerance protection \
	  is turned off for this virtual machine.\
       </description>\
       <cause>\
            <description> </description>\
            <action></action>\
        </cause>\
    </EventLongDescription>\
    "

VmFaultToleranceVmTerminatedEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmFaultToleranceVmTerminatedEvent">\
       <description>\
          A Primary VM or Secondary VM became inactive\
       </description>\
       <cause>\
            <description> The Secondary VM became inactive because its operations are no longer \
		synchronized with those of the Primary VM</description>\
            <action>vSphere HA will attempt to restart the Secondary VM</action>\
        </cause>\
       <cause>\
            <description> The Secondary VM became inactive because a hardware or network failure \
		caused the Primary VM to lose the Primary-to-Secondary connection</description>\
            <action>vSphere HA will attempt to restart the Secondary VM</action>\
        </cause>\
       <cause>\
            <description> The Fault Tolerant VM became inactive due to a partial hardware failure on \
		the physical host</description>\
            <action>vSphere HA will attempt to restart the Secondary VM</action>\
        </cause>\
       <cause>\
            <description> A user stopped the Fault Tolerant VM</description>\
            <action>The remaining Fault Tolerant VM takes over as the Primary VM. vSphere HA \
		will attempt to restart the Secondary VM.</action>\
        </cause>\
    </EventLongDescription>\
    "

VmMaxFTRestartCountReached.longDescription = "\
    <EventLongDescription id="vim.event.VmMaxFTRestartCountReached">\
       <description>\
          The system reached the maximum restart limit in its attempt to restart a Secondary VM\
       </description>\
       <cause>\
            <description>The system exceeded the number of allowed restart attempts for the Secondary VM \
		when it tried to reestablish Fault Tolerance</description>\
            <action>Check the causes for the restart failures and fix them. Then disable and re-enable Fault \
		Tolerance protection.</action>\
        </cause>\
    </EventLongDescription>\
    "

VmNoCompatibleHostForSecondaryEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmNoCompatibleHostForSecondaryEvent">\
       <description>\
          No compatible host was found when trying to place a Secondary VM\
       </description>\
       <cause>\
            <description>There was no compatible host available to place a Secondary VM</description>\
            <action>Resolve the incompatibilities and retry the operation</action>\
        </cause>\
    </EventLongDescription>\
    "

VmSecondaryDisabledBySystemEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmSecondaryDisabledBySystemEvent">\
       <description>\
          vCenter Server disabled a Secondary VM because it could not power on the Secondary VM\
       </description>\
       <cause>\
            <description>vCenter Server failed to power on the Secondary VM </description>\
            <action>Check the reason in the event message for more details, fix the failure, and \
		re-enable Fault Tolerance protection to power on the Secondary VM.</action>\
        </cause>\
    </EventLongDescription>\
    "

VmTimedoutStartingSecondaryEvent.longDescription = "\
    <EventLongDescription id="vim.event.VmTimedoutStartingSecondaryEvent">\
       <description> An attempt to start a Secondary VM timed out.\
       </description>\
       <cause>\
            <description>A user attempted to turn on or enable Fault Tolerance, triggering the start of \
		the Secondary VM. The start operation timed out and, as a result, vCenter Server disables \
		Fault Tolerance. </description>\
            <action>Fix any problems and re-enable Fault Tolerance protection</action>\
        </cause>\
       <cause>\
            <description>The secondary VM was started in response to a failure, but the start attempt \
		timed out</description>\
            <action> vSphere HA will attempt to power on the Secondary VM</action>\
        </cause>\
    </EventLongDescription>\
    "

CanceledHostOperationEvent.longDescription = "\
	<EventLongDescription id="vim.event.CanceledHostOperationEvent">\
		<description>\
			An operation performed on the host was canceled\
		</description>\
		<cause>\
			<description>\
		A previous event in the sequence of events will provide more information about the \
		cause of this cancellation\
			</description>\
		</cause>\
	</EventLongDescription>\
    "

ChangeOwnerOfFileFailedEvent.longDescription = "\
	<EventLongDescription id="vim.event.ChangeOwnerOfFileFailedEvent">\
		<description>\
			Changing the owner of a file or folder failed\
		</description>\
	</EventLongDescription>\
    "

HostAddFailedEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostAddFailedEvent">\
		<description>\
			Adding a host failed\
		</description>\
	</EventLongDescription>\
    "

HostAdminDisableEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostAdminDisableEvent">\
		<description>\
			Host permissions have been changed so that only the account used for \
			vCenter Server operations has Administrator permissions\
		</description>\
		<cause>\
			<description>\
				This condition occurs when vCenter Server removes all other Administrator \
				access to the host because the host has been placed in Lockdown Mode. \
				The host can be managed by vCenter Server only and \
				Only vCenter Server can re-enable Administrator access for other accounts.\
			</description>\
		</cause>\
	</EventLongDescription>\
    "

HostAdminEnableEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostAdminEnableEvent">\
		<description>\
			vCenter Server has restored Administrator permissions for host user accounts \
			 whose permissions were disabled by Lockdown Mode\
		</description>\
		<cause>\
			<description>\
				This condition occurs when vCenter Server restores Administrator access to \
				host user accounts that lost their Administrator permissions when the host was \
				placed in Lockdown Mode\
			</description>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedAccountFailedEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedAccountFailedEvent">\
		<description>\
			Could not connect to the host because setting up a management account failed\
		</description>\
		<cause>\
			<description>\
			The account used by vCenter Server to manage the host could not be configured\
			</description>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedAlreadyManagedEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedAlreadyManagedEvent">\
		<description>\
			Could not connect to the host because it is already being managed by a \
			different vCenter Server instance.\
		</description>\
		<cause>\
			<description>\
				The host is already being managed by a different vCenter Server instance\
			</description>\
			<action>\
				Remove the host from the inventory for the other vCenter Server instance\
			</action>\
			<action>\
				Force the addition of the host to the current vCenter Server instance\
			</action>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedBadCcagentEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedBadCcagentEvent">\
		<description>\
			Could not connect to the host because the host agent did not respond\
		</description>\
		<cause>\
			<description>\
				No response was received from the host agent\
			</description>\
			<action>\
				Restart the host agent on the ESX/ESXi host\
			</action>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedBadUsernameEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedBadUsernameEvent">\
		<description>\
			Could not connect to the host due to an invalid username and password combination\
		</description>\
		<cause>\
			<description>\
				Invalid username and password combination\
			</description>\
			<action>\
				Use the correct username and password\
			</action>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedBadVersionEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedBadVersionEvent">\
		<description>\
			Could not connect to the host due to an incompatible vSphere Client version\
		</description>\
		<cause>\
			<description>\
			The version of the vSphere Client is incompatible with the ESX/ESXi host so \
			the connection attempt failed\
			</description>\
			<action>\
			Download and use a compatible vSphere Client version to connect to the host\
			</action>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedCcagentUpgradeEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedCcagentUpgradeEvent">\
		<description>\
			Could not connect to the host because a host agent upgrade or \
			installation is in process\
		</description>\
		<cause>\
			<description>\
				The host agent is being upgraded or installed on the host\
			</description>\
			<action>\
				Wait for the host agent upgrade or installation to complete\
			</action>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedEvent">\
		<description>\
			Could not connect to the host due to an unspecified condition\
		</description>\
		<cause>\
			<description>\
				Unknown cause of failure\
			</description>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedNetworkErrorEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedNetworkErrorEvent">\
		<description>\
			Could not connect to the host due to a network error\
		</description>\
		<cause>\
			<description>\
				A Network error occurred while connecting to the host\
			</description>\
			<action>\
				Verify that host networking is configured correctly\
			</action>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedNoAccessEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedNoAccessEvent">\
		<description>\
			Could not connect to the host due to insufficient account privileges\
		</description>\
		<cause>\
			<description>\
				The account used to connect to host does not have host access privileges\
			</description>\
			<action>\
				Use an account that has sufficient privileges to connect to the host\
			</action>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedNoConnectionEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedNoConnectionEvent">\
		<description>\
			Could not connect to the host because the host is not in the network\
		</description>\
		<cause>\
			<description>\
				The host that you are attempting to connect to is not present in the network\
			</description>\
			<action>\
				Verify that host networking is configured correctly and the host is connected \
				to the same network as vCenter Server\
			</action>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedNoLicenseEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedNoLicenseEvent">\
		<description>\
			Could not connect to the host due to a licensing issue\
		</description>\
		<cause>\
			<description>\
				There are not enough licenses to add the host to the vCenter Server inventory. \
				This event is accompanied by a fault that specifies the missing licenses \
				required to add the host successfully.\
			</description>\
			<action>\
				Add the necessary licenses to vCenter Server and try adding the host again\
			</action>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedNotFoundEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedNotFoundEvent">\
		<description>\
			Could not connect to the host because vCenter Server could not resolve the host name\
		</description>\
		<cause>\
			<description>\
				Unable to resolve the host name of the host\
			</description>\
			<action>\
				Verify that the correct host name has been supplied for the host\
			</action>\
			<action>\
				Configure the host to use a known-good (resolvable) host name\
			</action>\
			<action>\
				Add the host name to the DNS server\
			</action>\
		</cause>\
	</EventLongDescription>\
    "

HostCnxFailedTimeoutEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostCnxFailedTimeoutEvent">\
		<description>\
			Could not connect to the host because the connection attempt timed out\
		</description>\
		<cause>\
			<description>\
				A timeout occurred while attempting to connect to the host\
			</description>\
		</cause>\
	</EventLongDescription>\
    "

HostConnectionLostEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostConnectionLostEvent">\
		<description>\
			Connection to the host has been lost\
		</description>\
		<cause>\
			<description>\
				The host is not in a state where it can respond\
			</description>\
		</cause>\
	</EventLongDescription>\
    "

HostReconnectionFailedEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostReconnectionFailedEvent">\
		<description>\
			Could not reestablish a connection to the host\
		</description>\
		<cause>\
			<description>\
				The host is not in a state where it can respond\
			</description>\
		</cause>\
	</EventLongDescription>\
    "

TimedOutHostOperationEvent.longDescription = "\
	<EventLongDescription id="vim.event.TimedOutHostOperationEvent">\
		<description>\
			An operation performed on the host has timed out\
		</description>\
		<cause>\
			<description>\
			A previous event in the sequence of events will provide information on the \
			reason for the timeout\
			</description>\
		</cause>\
	</EventLongDescription>\
    "

AccountCreatedEvent.longDescription = "\
	<EventLongDescription id="vim.event.AccountCreatedEvent">\
		<description>\
			An account has been created on the host\
		</description>\
	</EventLongDescription>\
    "

AccountRemovedEvent.longDescription = "\
	<EventLongDescription id="vim.event.AccountRemovedEvent">\
		<description>\
			An account has been removed from the host\
		</description>\
	</EventLongDescription>\
    "

AccountUpdatedEvent.longDescription = "\
	<EventLongDescription id="vim.event.AccountUpdatedEvent">\
		<description>\
			An account has been updated on the host\
		</description>\
	</EventLongDescription>\
    "

AdminPasswordNotChangedEvent.longDescription = "\
	<EventLongDescription id="vim.event.AdminPasswordNotChangedEvent">\
		<description>\
			The default password for the Administrator user on the host has not been changed\
		</description>\
		<cause>\
			<description>\
			You have not changed the password for the Administrator user on the host so the \
			default password is still active\
			</description>\
			<action>\
				Change the password for the Administrator user on the host\
			</action>\
		</cause>\
	</EventLongDescription>\
    "

BadUsernameSessionEvent.longDescription = "\
	<EventLongDescription id="vim.event.BadUsernameSessionEvent">\
		<description>\
			A user attempted to log in with an unknown or invalid username\
		</description>\
		<cause>\
            <description>\
			The username is unknown to the system\
			</description>\
            <action>\
			Use a username that is included in the system user directory\
			</action>\
            <action>\
			On Linux, verify that the user directory is correctly configured\
			</action>\
            <action>\
			If you are using Active Directory, check the health of the domain controller\
			</action>\
        </cause>\
        <cause>\
            <description>\
			The user provided an invalid password\
			</description>\
            <action>\
			Supply the correct password\
			</action>\
        </cause>\
	</EventLongDescription>\
    "

ErrorUpgradeEvent.longDescription = "\
	<EventLongDescription id="vim.event.ErrorUpgradeEvent">\
		<description>\
			An error occurred during agent upgrade\
		</description>\
	</EventLongDescription>\
    "

GeneralHostErrorEvent.longDescription = "\
	<EventLongDescription id="vim.event.GeneralHostErrorEvent">\
		<description>\
			An error occurred on the host\
		</description>\
		<cause>\
            <description>\
			The agent cannot send heartbeats because of a networking related failure on host\
			</description>\
        </cause>\
        <cause>\
            <description>\
			The agent failed to update the configuration file on host\
			</description>\
        </cause>\
        <cause>\
            <description>\
			The agent failed to save the configuration file to disk on host\
			</description>\
        </cause>\
        <cause>\
            <description>\
			The provisioning module failed to load. As a result, all provisioning operations will \
			fail on host.\
			</description>\
        </cause>\
	</EventLongDescription>\
    "

GeneralHostInfoEvent.longDescription = "\
	<EventLongDescription id="vim.event.GeneralHostInfoEvent">\
		<description>\
			A general information event occurred on the host\
		</description>\
	</EventLongDescription>\
    "

GeneralHostWarningEvent.longDescription = "\
	<EventLongDescription id="vim.event.GeneralHostWarningEvent">\
		<description>\
			A general warning event occurred on the host\
		</description>\
		<cause>\
            <description>\
			Virtual machine creation might fail because the agent was unable to retrieve virtual \
			machine creation options from the host\
			</description>\
        </cause>\
	</EventLongDescription>\
    "

GeneralUserEvent.longDescription = "\
	<EventLongDescription id="vim.event.GeneralUserEvent">\
		<description>\
			A general user event occurred on the host\
		</description>\
		<cause>\
            <description>\
			A user initiated an action on the host\
			</description>\
        </cause>\
	</EventLongDescription>\
    "

GeneralVmErrorEvent.longDescription = "\
	<EventLongDescription id="vim.event.GeneralVmErrorEvent">\
		<description>\
			An error occurred on the virtual machine\
		</description>\
	</EventLongDescription>\
    "

GeneralVmInfoEvent.longDescription = "\
	<EventLongDescription id="vim.event.GeneralVmInfoEvent">\
		<description>\
			A general information event occurred on the virtual machine\
		</description>\
	</EventLongDescription>\
    "

GeneralVmWarningEvent.longDescription = "\
	<EventLongDescription id="vim.event.GeneralVmWarningEvent">\
		<description>\
			A general warning event occurred on the virtual machine\
		</description>\
	</EventLongDescription>\
    "

HostSyncFailedEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostSyncFailedEvent">\
		<description>\
			Failed to sync with the vCenter Agent on the host\
		</description>\
		<cause>\
            <description>\
				The event contains details on why this failure occurred\
			</description>\
        </cause>\
	</EventLongDescription>\
    "

HostUpgradeFailedEvent.longDescription = "\
	<EventLongDescription id="vim.event.HostUpgradeFailedEvent">\
		<description>\
			Failed to connect to the host due to an installation or upgrade issue\
		</description>\
	</EventLongDescription>\
    "

NoAccessUserEvent.longDescription = "\
	<EventLongDescription id="vim.event.NoAccessUserEvent">\
		<description>\
			A user could not log in due to insufficient access permission\
		</description>\
		<cause>\
            <description>\
			The user account has insufficient access permission\
			</description>\
			<action>\
			Log in with a user account that has the necessary access permissions or grant \
			additional access permissions to the current user\
			</action>\
        </cause>\
	</EventLongDescription>\
    "

SessionTerminatedEvent.longDescription = "\
	<EventLongDescription id="vim.event.SessionTerminatedEvent">\
		<description>\
			A session has been terminated\
		</description>\
	</EventLongDescription>\
    "

TaskTimeoutEvent.longDescription = "\
	<EventLongDescription id="vim.event.TaskTimeoutEvent">\
		<description>\
			A task has been cleaned up because it timed out\
		</description>\
	</EventLongDescription>\
    "

UserUpgradeEvent.longDescription = "\
	<EventLongDescription id="vim.event.UserUpgradeEvent">\
		<description>\
			A general user event occurred due to an upgrade\
		</description>\
	</EventLongDescription>\
    "

VcAgentUninstalledEvent.longDescription = "\
	<EventLongDescription id="vim.event.VcAgentUninstalledEvent">\
		<description>\
			The vCenter Agent has been uninstalled from host\
		</description>\
	</EventLongDescription>\
    "

VcAgentUninstallFailedEvent.longDescription = "\
	<EventLongDescription id="vim.event.VcAgentUninstallFailedEvent">\
		<description>\
			An attempt to uninstall the vCenter Agent failed on the host\
		</description>\
		<cause>\
            <description>\
				The event contains details on why this failure occurred\
			</description>\
        </cause>\
	</EventLongDescription>\
    "

VcAgentUpgradedEvent.longDescription = "\
	<EventLongDescription id="vim.event.VcAgentUpgradedEvent">\
		<description>\
			The vCenter Agent has been upgraded on the host\
		</description>\
	</EventLongDescription>\
    "

VcAgentUpgradeFailedEvent.longDescription = "\
	<EventLongDescription id="vim.event.VcAgentUpgradeFailedEvent">\
		<description>\
			A vCenter Agent upgrade attempt failed on the host\
		</description>\
		<cause>\
            <description>\
				The event contains details on why this failure occurred\
			</description>\
        </cause>\
	</EventLongDescription>\
    "

VimAccountPasswordChangedEvent.longDescription = "\
	<EventLongDescription id="vim.event.VimAccountPasswordChangedEvent">\
		<description>\
			The password for the Vim account user on the host has been changed. \
			This account is created by vCenter Server and used to manage the host.\
		</description>\
		<cause>\
            <description>\
			vCenter Server periodically changes the password of the Vim account that it \
			uses to manage the host\
			</description>\
        </cause>\
	</EventLongDescription>\
    "

VmMessageErrorEvent.longDescription = "\
	<EventLongDescription id="vim.event.VmMessageErrorEvent">\
		<description>\
			An error message listing a collection of observations has been reported by the virtual machine\
		</description>\
		<cause>\
            <description>\
				The event contains details on why this error occurred\
			</description>\
        </cause>\
	</EventLongDescription>\
    "

VmMessageEvent.longDescription = "\
	<EventLongDescription id="vim.event.VmMessageEvent">\
		<description>\
			An information message listing a collection of observations has been reported by the virtual machine\
		</description>\
		<cause>\
            <description>\
				The event contains details on the messages from the virtual machine\
			</description>\
        </cause>\
	</EventLongDescription>\
    "

VmMessageWarningEvent.longDescription = "\
	<EventLongDescription id="vim.event.VmMessageWarningEvent">\
		<description>\
			A warning message listing a collection of observations has been reported by the virtual machine\
		</description>\
		<cause>\
            <description>\
				The event contains details on why this warning was issued\
			</description>\
        </cause>\
	</EventLongDescription>\
    "

DvsHostWentOutOfSyncEvent.longDescription = "\
    <EventLongDescription id="vim.event.DvsHostWentOutOfSyncEvent">\
       <description> The vSphere Distributed Switch configuration on the host differed from that of the vCenter Server\
       </description>\
       <cause>\
         <description> The host was not connected to the vCenter Server when updates were sent </description>\
       </cause>\
       <cause>\
         <description> vCenter Server failed to push the vSphere Distributed Switch configuration to the host in the past</description>\
       </cause>\
    </EventLongDescription>\
    "

GhostDvsProxySwitchDetectedEvent.longDescription = "\
    <EventLongDescription id="vim.event.GhostDvsProxySwitchDetectedEvent">\
       <description> \
          vCenter Server found a vSphere Distributed Switch proxy switch on the host that does not match any \
          vSphere Distributed Switch in vCenter Server \
       </description>\
       <cause>\
            <description> \
               The vSphere Distributed Switch corresponding to the vSphere Distributed Switch proxy switch \
               on the host was deleted while host was disconnected from the vCenter Server\
            </description>\
        </cause>\
       <cause>\
            <description> \
               The host is no longer a member of the vSphere Distributed Switch that the proxy switch in the host \
               corresponds to \
            </description>\
        </cause>\
    </EventLongDescription>\
    "

IncorrectHostInformationEvent.longDescription = "\
    <EventLongDescription id="vim.event.IncorrectHostInformationEvent">\
       <description> The host did not provide the information needed to acquire the correct set of licenses </description>\
       <cause>\
            <description> The cpuCores, cpuPackages or hostType information on the host is not valid </description>\
        </cause>\
       <cause>\
            <description> The host information is not available because host was added as disconnected </description>\
        </cause>\
    </EventLongDescription>\
    "

HostWwnConflictEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostWwnConflictEvent">\
       <description> \
          The WWN (World Wide Name) of this host conflicts with the WWN of another host or virtual machine\
       </description>\
       <cause>\
            <description> The WWN of this host conflicts with WWN of another host </description>\
       </cause>\
       <cause>\
            <description> The WWN of this host conflicts with WWN of another virtual machine</description>\
       </cause>\
    </EventLongDescription>\
    "

HostIpChangedEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostIpChangedEvent">\
       <description> \
          The IP address of the host was changed\
       </description>\
       <cause>\
            <description> The IP address of the host was changed through vCenter Server </description>\
       </cause>\
       <cause>\
            <description> The IP address of the host was changed through the host </description>\
       </cause>\
    </EventLongDescription>\
    "

DrsExitStandbyModeFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.DrsExitStandbyModeFailedEvent">\
       <description>\
          DPM failed to power on a host in standby mode. \
		  DPM tried to power on a host using IPMI, iLO or Wake-on-LAN protocol, but the host \
		  did not power on.\
       </description>\
       <cause>\
            <description>DPM could not communicate with the BMC on the host</description>\
            <action>Verify the IPMI/iLO credentials entered in vCenter Server</action>\
            <action>Verify that LAN access is enabled in the BMC</action>\
        </cause>\
        <cause>\
            <description>The vMotion NIC on the host does not support Wake-on-LAN</description>\
            <action>Select a vMotion NIC that supports Wake-on-LAN</action>\
        </cause>\
    </EventLongDescription>\
    "

ClusterOvercommittedEvent.longDescription = "\
    <EventLongDescription id="vim.event.ClusterOvercommittedEvent">\
       <description>\
          The cumulative CPU and/or memory resources of all hosts in the cluster \
          are not adequate to satisfy the resource reservations of all virtual machines in the \
          cluster\
       </description>\
       <cause>\
            <description>You attempted to power on a virtual machine bypassing vCenter Server. \
		This condition occurs when you attempt the power on using the vSphere Client directly \
		connected to the host.</description>\
            <action>In a DRS cluster, do not power on virtual machines bypassing vCenter Server</action>\
        </cause>\
        <cause>\
            <description>A host was placed in Maintenance, Standby, or Disconnected Mode</description>\
            <action>Bring any host in Maintenance, Standby, or Disconnected mode out of these modes</action>\
        </cause>\
    </EventLongDescription>\
    "

ResourceViolatedEvent.longDescription = "\
    <EventLongDescription id="vim.event.ResourceViolatedEvent">\
       <description>\
          The cumulative CPU and/or memory resource consumption of all virtual machines in the \
          resource pool exceeds the resource pool configuration \
       </description>\
       <cause>\
            <description>You attempted to move a virtual machine from one resource pool into another \
		bypassing vCenter Server. This condition occurs when you attempt the move using \
		the vSphere Client directly connected to the host.\
		</description>\
            <action>In a DRS cluster, do not move and power on a virtual machine bypassing vCenter Server</action>\
        </cause>\
    </EventLongDescription>\
    "

HostComplianceCheckedEvent.longDescription = "\
   <EventLongDescription id="vim.event.HostComplianceCheckedEvent">\
      <description>\
         The host was checked for compliance with a host profile\
      </description>\
      <cause>\
         <description>\
            The user initiated a compliance check on the host against a host profile \
          </description>\
      </cause>\
      <cause>\
         <description>\
            A scheduled task initiated a compliance check for \
            the host against a host profile \
         </description>\
      </cause>\
    </EventLongDescription>\
    "

ClusterComplianceCheckedEvent.longDescription = "\
   <EventLongDescription id="vim.event.ClusterComplianceCheckedEvent">\
      <description>\
         The cluster was checked for compliance with a cluster profile\
      </description>\
      <cause>\
         <description>\
            The user initiated a compliance check on the cluster against a cluster profile \
         </description>\
      </cause>\
      <cause>\
         <description>\
            A scheduled has initiated a compliance check for \
            the cluster against a cluster profile \
         </description>\
      </cause>\
    </EventLongDescription>\
    "

HostNonCompliantEvent.longDescription = "\
   <EventLongDescription id="vim.event.HostNonCompliantEvent">\
      <description>\
         The host does not comply with the host profile\
       </description>\
       <cause>\
          <description>\
             The host is not in compliance with the attached profile \
          </description>\
       <action>\
          Check the Summary tab for the host in the vSphere Client to determine the \
          possible cause(s) of noncompliance \
       </action>\
       </cause>\
</EventLongDescription>\
   "

ClusterReconfiguredEvent.longDescription = "\
    <EventLongDescription id="vim.event.ClusterReconfiguredEvent">\
       <description>\
          The cluster configuration was changed. The cluster configuration includes \
          information about the DRS, DPM, EVC and vSphere HA settings of the cluster. All DRS \
          rules are also stored in the cluster configuration. Editing the cluster \
          configuration may trigger an invocation of DRS and/or enabling/disabling \
          of vSphere HA on each host in the cluster. \
       </description>\
    </EventLongDescription>\
    "

ClusterStatusChangedEvent.longDescription = "\
    <EventLongDescription id="vim.event.ClusterStatusChangedEvent">\
       <description>\
          The cluster status has changed. This status is the status of the root resource \
          pool that encompasses the entire cluster. A cluster status change may be \
          accompanied by the removal of a configuration issue if one was previously detected. \
          A cluster status of green indicates that everything is fine. A yellow status \
          indicates that the root resource pool does not have the resources to meet the \
          reservations of its children. A red status means that a node in the resource \
          pool has children whose reservations exceed the configuration of the node. \
       </description>\
       <cause>\
            <description>The cluster status changed to yellow</description>\
            <action>Add more resources (more hosts), or reduce the reservation of the \
            resource pools directly under the root to match the new capacity</action>\
        </cause>\
        <cause>\
            <description>The cluster status changed to red</description>\
            <action>Change the resource settings on the resource pools that are red so \
            that they can accommodate their child virtual machines. If this is not possible, lower \
            the virtual machine reservations. If this is not possible either, power off some \
	    virtual machines.</action>\
        </cause>\
    </EventLongDescription>\
    "

DrsInvocationFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.DrsInvocationFailedEvent">\
       <description>\
          A DRS invocation failed to complete successfully. This condition can occur for a \
		  variety of reasons, some of which may be transient. \
       </description>\
       <cause>\
            <description>An error was encountered during a DRS invocation</description>\
            <action>Disable and re-enable DRS</action>\
        </cause>\
    </EventLongDescription>\
    "

DrsResourceConfigureFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.DrsResourceConfigureFailedEvent">\
       <description>\
          The DRS resource settings could not be successfully applied to a host in the \
		  cluster. This condition is typically transient. \
       </description>\
       <cause>\
            <description>DRS resource settings could not be applied to a host.</description>\
            <action>DRS generates resource settings that map the cluster values to the \
            host. However, in this case, the values could not be successfully applied \
            to the host. This is typically a transient error caused by delayed synchronization \
            from DRS to the host. If this condition persists, enable debug logging in vpxa and \
	    contact VMware Support. </action>\
        </cause>\
    </EventLongDescription>\
    "

DrsVmMigratedEvent.longDescription = "\
    <EventLongDescription id="vim.event.DrsVmMigratedEvent">\
       <description>\
          A virtual machine was migrated based on a DRS recommendation. The recommendation might \
		  have been made be to achieve better load balancing in the cluster or to evacuate \
		  a host in the cluster that is being put into Standby or Maintenance Mode. \
       </description>\
       <cause>\
            <description>DRS recommended the migration of a virtual machine</description>\
        </cause>\
    </EventLongDescription>\
    "

DrsVmPoweredOnEvent.longDescription = "\
    <EventLongDescription id="vim.event.DrsVmPoweredOnEvent">\
       <description>\
          A virtual machine was powered on by the user and DRS choose a host for the virtual machine based on \
	  the current cluster load distribution combined with the virtual machine's resource requirements \
       </description>\
       <cause>\
            <description>DRS chose a host for a virtual machine that was being powered on</description>\
        </cause>\
    </EventLongDescription>\
    "

HostOvercommittedEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostOvercommittedEvent">\
       <description>\
          A host does not have sufficient CPU and/or memory capacity to \
		  satisfy its resource configuration. The host has its own admission control, so this \
		  condition should never occur.\
       </description>\
       <cause>\
            <description>A host has insufficient capacity for its resource configuration</description>\
            <action>If you encounter this condition, contact VMware Support </action>\
	</cause>\
    </EventLongDescription>\
    "

HostStatusChangedEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostStatusChangedEvent">\
       <description>\
          The host status has changed. This status is the status of the root resource \
          pool that encompasses the entire host. A host status change may be \
          accompanied by the removal of a configuration issue if one was previously detected. \
          A host status of green indicates that everything is fine. A yellow status \
          indicates that the root resource pool does not have the resources to meet the \
          reservations of its children. A red status means that a node in the resource \
          pool has children whose reservations exceed the configuration of the node. \
       </description>\
       <cause>\
            <description>The host status changed to yellow</description>\
            <action>Reduce the reservation of the resource pools directly under the \
            root to match the new capacity</action>\
        </cause>\
        <cause>\
            <description>The host status changed to red</description>\
            <action>Change the resource settings on the resource pools that are red so \
            that they can accommodate their child virtual machines. If this is not possible, lower \
            the virtual machine reservations. If this is not possible either, power off some \
	    virtual machines.</action>\
        </cause>\
    </EventLongDescription>\
    "

NoMaintenanceModeDrsRecommendationForVM.longDescription = "\
    <EventLongDescription id="vim.event.NoMaintenanceModeDrsRecommendationForVM">\
       <description>\
          DRS failed to generate a vMotion recommendation for a virtual machine on a host entering \
		  Maintenance Mode. This condition typically occurs because no other host \
		  in the DRS cluster is compatible with the virtual machine. Unless you manually \
		  migrate or power off this virtual machine, the host will be unable to enter \
		  Maintenance Mode. \
       </description>\
       <cause>\
            <description>DRS failed to evacuate a powered on virtual machine</description>\
            <action>Manually migrate the virtual machine to another host in the cluster</action>\
            <action>Power off the virtual machine</action>\
            <action>Bring any hosts in Maintenance Mode out of that mode</action>\
            <action>Cancel the task that is making the host enter Maintenance Mode </action>\
        </cause>\
    </EventLongDescription>\
    "

NotEnoughResourcesToStartVmEvent.longDescription = "\
    <EventLongDescription id="vim.event.NotEnoughResourcesToStartVmEvent">\
       <description>\
          This event is issued by vSphere HA when the master agent was not able to fail over \
	  a virtual machine to one of its compatible hosts. This condition is due to one or \
	  more of the causes listed below. When this condition occurs, vSphere HA will report \
	  a cause for it in the event summary, but note that additional causes might exist.\
	  It is more likely to occur if vSphere HA admission \
	  control is disabled or more hosts fail than were provisioned for. When a virtual \
	  machine cannot be placed, vSphere HA will retry placing it when the cluster state \
	  changes. Also, if vSphere DRS is enabled, it will be invoked to try to defragment \
	  the cluster or bring hosts out of Standby Mode.\
       </description>\
       <cause>\
            <description>\
            A virtual machine has bandwidth reservations for CPU, memory, vFlash cache, or virtual NICs. \
	            There was no compatible host that had enough resources to satisfy \
	            the reservations.\
            </description>\
            <action>Decrease the virtual machine resource reservation</action>\
            <action>Add more host(s) to cluster</action>\
            <action>Bring online any failed hosts or resolve a network partition if one exists</action>\
            <action>If DRS is in manual mode, look for any pending recommendations \
            and approve them so that vSphere HA failover can proceed</action>\
        </cause>\
        <cause>\
            <description>\
	         The cluster has vSAN enabled, and one or more hosts that contribute storage\
               to the cluster is inaccessible, preventing vSphere HA from powering on the virtual machine.\
               This applies to virtual machines that have one or more files on a vSAN datastore.\
            </description>\
            <action>Bring online any failed hosts or resolve a network partition if one \
            exists that involves hosts that contribute storage to the vSAN cluster</action>\
        </cause>\
        <cause>\
            <description>One or more datastores that are associated with a virtual machine are \
               inaccessible by any compatible host in the cluster.</description>\
            <action>Bring online any non-responding host that mounts the virtual machine datastores</action>\
            <action>Fix the all-paths-down (APD) or permanent-device-loss (PDL) issues.</action>\
        </cause>\
        <cause>\
            <description>vSphere HA is enforcing virtual machine to virtual machine \
               anti-affinity rules, and the rule cannot be satisfied. </description>\
            <action>Add more hosts to cluster</action>\
            <action>Bring online any non-responding host or resolve a network partition if one exists</action>\
            <action>Remove any anti-affinity rules that are restricting the placement</action>\
        </cause>\
        <cause>\
            <description>The number of VMs that can run on each host is limited. \
               There is no host that can power on the VM without exceeding the limit.</description>\
            <action>Increase the limi if you have set the limitVmsPerESXHost HA advanced option.</action>\
            <action>Bring online any non-responding host or add new hosts to the cluster</action>\
        </cause>\
    </EventLongDescription>\
    "

ResourcePoolReconfiguredEvent.longDescription = "\
    <EventLongDescription id="vim.event.ResourcePoolReconfiguredEvent">\
       <description>\
          The resource pool configuration changed. The resource pool configuration \
          includes information about the resource reservations of the resource pool and \
          the resource reservations of its children. \
       </description>\
    </EventLongDescription>\
    "

DasHostIsolatedEvent.longDescription = "\
    <EventLongDescription id="vim.event.DasHostIsolatedEvent">\
       <description>\
          vSphere HA detected that the host is network isolated. When a host is in this state, vSphere HA \
          applies the power-off or shutdown host isolation response to virtual machines running on the host, and \
          continues to monitor the virtual machines that are left powered on. While a host is in this state, vSphere HA's \
          ability to restart virtual machines after a failure is impacted. vSphere HA only powers off or shuts down a \
          virtual machine if the agent on the host determines that a master agent is responsible for the virtual machine. \
       </description>\
       <cause>\
            <description> \
                A host is network isolated if both of the following conditions are met: (1) \
                isolation addresses have been configured and the host is unable to ping them; (2) \
                the vSphere HA agent on the host is unable to access any of the agents running on the other cluster hosts. \
            </description>\
            <action>\
                 Resolve the networking problem that is preventing the host from pinging its isolation\
                 addresses and communicating with other hosts. Ensure that there is redundancy in the \
                 management networks used by vSphere HA. With redundancy, vSphere HA is able to communicate \
                over more than one path thus reducing the chance of a host becoming isolated. \
            </action>\
       </cause>\
    </EventLongDescription>\
    "

HostMissingNetworksEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostMissingNetworksEvent">\
       <description>\
       The host being added to the vSphere HA cluster has fewer management networks than \
       existing hosts in the cluster. When vSphere HA is being configured for a host, an existing \
       host in the cluster is examined for the networks used by vSphere HA for heartbeats \
       and other vSphere HA communication.  The joining host is expected to have the same \
       number of management networks, and optimally, have common subnets.  This \
       helps facilitate the pairing of source/destination pairs for heartbeats. \
       If common subnets are not detected (using the IP address/subnet mask) between \
       the member being added and the existing members of the cluster, this event is \
       generated and the configuration task fails. The event details report the \
       subnets of the existing member that are not present on the joining member. \
       </description>\
       <cause>\
            <description>\
                The host does not have networks compatible with an existing cluster member\
            </description>\
            <action>\
                Change the host's network configuration to enable vSphere HA traffic on the same \
                subnets as existing hosts in the cluster. vSphere HA will use the Service Console \
                port groups on ESX and, on ESXi hosts, the port groups with the "Management Traffic" \
                checkbox selected. After you change the host's network configuration, reconfigure \
		vSphere HA for this host.\
            </action>\
            <action>\
                Use advanced options to override the default port group selection for vSphere HA \
                cluster communication. You can use the das.allowNetwork[X] advanced option \
                to tell vSphere HA to use the port group specified in this option. \
                For each port group name that should be used, specify one das.allowNetwork[X] \
                advanced option. The vSphere HA configuration examines the host being added for \
                port groups that match the name specified. The configuration task also examines \
                an existing member whose port groups match the name specified. The number of \
                matched port group names must be the same on each host. After setting the advanced \
		options, re-enable vSphere HA for this cluster.\
            </action>\
       </cause>\
    </EventLongDescription>\
    "

HostExtraNetworksEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostExtraNetworksEvent">\
       <description>\
       The host being added to the vSphere HA cluster has more management networks than \
       existing hosts in the cluster. When vSphere HA is being configured for a host, an existing \
       host in the cluster is examined for the networks used by vSphere HA for heartbeats \
       and other vSphere HA communication. The joining host is expected to have the same \
       number of management networks, and optimally, be on the same subnets. This \
       helps to facilitate the pairing up of source/destination pairs for heartbeats. \
       If common subnets are not detected (using the IP address/subnet mask) between \
       the member being added and the existing members of the cluster, this event is \
       generated and the configuration task fails. The event details report the \
       subnet of the joining member that are not present on the existing member. \
       </description>\
       <cause>\
            <description>\
                The host has extra networks missing on an existing cluster member\
            </description>\
            <action>\
                Change the host's network configuration to enable vSphere HA traffic on the same \
                subnets as existing hosts in the cluster. vSphere HA will use the Service Console \
                port groups on ESX and, on ESXi hosts, the port groups with the "Management Traffic" \
                checkbox selected.\
            </action>\
            <action>\
                Use advanced options to override the default port group selection for vSphere HA \
                cluster communication.  You can use the das.allowNetwork[X] advanced option \
                to tell vSphere HA to use the port group specified in this option. \
                For each port group name that should be used, specify one das.allowNetwork[X] \
                advanced option.  The vSphere HA configuration examines the host being added for \
                port groups that match the name specified. The configuration task also examines \
                an existing member whose port groups match the name specified. The number of \
                matched port group names must be the same on each host.  After setting the advanced \
                options, re-enable vSphere HA for the cluster.\
            </action>\
       </cause>\
    </EventLongDescription>\
    "

HostNoHAEnabledPortGroupsEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostNoHAEnabledPortGroupsEvent">\
       <description>\
       vSphere HA has determined that there are no management networks available on the \
       host for vSphere HA inter-agent communication.\
       </description>\
       <cause>\
            <description>\
                The host has no vSphere HA management networks available\
            </description>\
            <action>\
                If this event is observed when the host is being added to a vSphere HA cluster, \
                change the host's network configuration to enable vSphere HA traffic on one or \
                more port groups. By default, vSphere HA will use the Service Console port groups \
                on ESX and ESXi hosts, the port groups with the Management Traffic checkbox \
                selected. If vSphere HA was already configured on the host, it is possible that the \
                host's network settings have changed and invalidated the management network \
                configuration. Review the settings to make sure the port groups configured for \
                managment network still exist on the host and for ESXi the Management Traffic option \
                is enabled. Reconfigure vSphere HA on the host after fixing any configuration issues.\
            </action>\
       </cause>\
    </EventLongDescription>\
    "

HostNoAvailableNetworksEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostNoAvailableNetworksEvent">\
       <description>\
       The host being added to the vSphere HA cluster has no management networks available for \
       vSphere HA cluster communication. The advanced option das.allowNetwork[X] is set, but no \
       port group names match the advanced option for this host.\
       </description>\
       <cause>\
            <description>\
                The host has no port groups that match the names used by the advanced options \
                to control which port groups vSphere HA uses\
            </description>\
            <action>\
                Delete the advanced options das.allowNetwork[X] to allow vSphere HA to select the default \
                management port groups\
            </action>\
            <action>\
                Correct the names of the port groups specified in the advanced options to match those \
                to be used by vSphere HA for this host\
            </action>\
            <action>\
                Specify additional das.allowNetwork[X] advanced options to match the port group names \
                for this host\
            </action>\
       </cause>\
    </EventLongDescription>\
    "

HostIsolationIpPingFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostIsolationIpPingFailedEvent">\
       <description>\
        vSphere HA was unable to ping one or more of the isolation IP addresses. The inabilikty to ping the addresses \
        may cause HA to incorrectly declare the host as network isolated. A host is declared as isolated if it cannot \
        ping the configured isolation addresses and the vSphere HA agent on the host is unable to access any of the \
        agents running on the other cluster hosts. \
       </description>\
       <cause>\
            <description>Could not ping the isolation address</description>\
            <action>Correct the cause of the failure to ping the address</action>\
            <action>\
                Use advanced options to change the addresses used by vSphere HA for determining if a host is \
                network isolated. By default, the isolation address is the default \
        	gateway of the management network. You can override the default using advanced options, or \
        	specify additional addresses to use for determining if a host is network isolated.  \
        	Set the das.useDefaultIsolationAddress advanced option to "false" if you prefer that \
		vSphere HA not use the default gateway as the isolation address. Specify the das.isolationAddress[X] \
		advanced option for each isolation address that you want to specify. The new values \
        	take effect when vSphere HA is reconfigured for each host.\
            </action>\
       </cause>\
    </EventLongDescription>\
    "

HostNoRedundantManagementNetworkEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostNoRedundantManagementNetworkEvent">\
       <description>\
       vSphere HA has determined that there is only one path for vSphere HA management traffic, \
       resulting in a single point of failure.  Best practices require \
       more than one path for vSphere HA to use for heartbeats and cluster communication.  \
       A host with a single path is more likely to be declared dead, network partitioned or \
       isolated after a network failure. If declared dead, vSphere HA will not respond if the host \
       subsequently actually fails, while if declared isolated, vSphere HA may apply the isolation \
       response thus impacting the uptime of the virtual machines running on it.\
       </description>\
       <cause>\
            <description>There is only one port group available for vSphere HA communication</description>\
            <action>Configure another Service Console port group on the ESX host</action>\
            <action>\
                Configure another port group on the ESXi host by selecting the "Management Traffic" \
		check box\
            </action>\
            <action>\
                Use NIC teaming on the management port group to allow ESX or ESXi to direct management \
                traffic out of more than one physical NIC in case of a path failure\
            </action>\
            <action>\
                If you accept the risk of not having redundancy for vSphere HA communication, you can \
                eliminate the configuration issue by setting the \
                das.ignoreRedundantNetWarning advanced option to "true"\
            </action>\
       </cause>\
    </EventLongDescription>\
    "

HostIpToShortNameFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostIpToShortNameFailedEvent">\
       <description>\
          The host's IP address could not be resolved to a short name \
       </description>\
       <cause>\
            <description>The host or DNS records are improperly configured</description>\
            <action>Check the host network configuration</action>\
            <action>Check the DNS configuration</action>\
        </cause>\
    </EventLongDescription>\
    "

HostGetShortNameFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostGetShortNameFailedEvent">\
       <description>\
          The hostname -s command has failed on the host \
       </description>\
       <cause>\
            <description>The host network is improperly configured</description>\
            <action>Check the host network configuration</action>\
        </cause>\
    </EventLongDescription>\
    "

HostPrimaryAgentNotShortNameEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostPrimaryAgentNotShortNameEvent">\
       <description>\
          The primary agent is not specified in short name format \
       </description>\
       <cause>\
            <description>The host network is improperly configured</description>\
            <action>Check the host network configuration</action>\
        </cause>\
    </EventLongDescription>\
    "

HostShortNameInconsistentEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostShortNameInconsistentEvent">\
       <description>\
          The name resolution check on the host returns different names for the host \
       </description>\
       <cause>\
            <description>The host network is improperly configured</description>\
            <action>Check the host network configuration</action>\
            <action>Check the DNS configuration</action>\
        </cause>\
    </EventLongDescription>\
    "

HostShortNameToIpFailedEvent.longDescription = "\
    <EventLongDescription id="vim.event.HostShortNameToIpFailedEvent">\
       <description>\
          The short name of the host can not be resolved to an IP address \
       </description>\
       <cause>\
            <description>The host network is improperly configured</description>\
            <action>Check the host network configuration</action>\
            <action>Check the DNS configuration</action>\
        </cause>\
    </EventLongDescription>\
    "

Ms-Dos/Windows Unix Write backup

jsp File Browser version 1.2 by www.vonloesch.de