“Cannot run upgrade script on host” during upgrade from ESXi 5.1 to ESXi 5.5

The host upgrade from ESXi 5.1 to ESXi 5.5 failed at 93 percent with the following error: „Cannot execute upgrade script on host“.

cannot_execute_script

I found two possible issues – the second one worked for me:

Issue 1: /bootbank/state.xxxxxxxx directory not empty

Take a look at KB 2007163 „Upgrading a VMware ESXi host fails with the error: Cannot run upgrade script on host“

Issue 2: troubles with the FDM agent (former HA agent) from the host

In my case issue 2 was the problem – performing the steps descriped below did the trick for me.

I found the following message in the /var/log/vua.log:

[FFD0D8C0 error ‘Default’] Alert:WARNING: This application is not using QuickExit().

The exit code will be set to 0.@ bora/vim/lib/vmacore/main/service.cpp:147

–> Backtrace:

–> backtrace[00] rip 1bc228c3 Vmacore::System::Stacktrace::CaptureFullWork(unsigned int)

Resolution:

  • disable HA for the cluster
  • remove the ESXi host from the cluster
  • connect  via SSH to the ESXi host and run the following commands to uninstall the FDM agent:

(as also descriped in KB 1003714 „Verifying and reinstalling the correct version of the VMware vCenter Server agents”)

cp /opt/vmware/uninstallers/VMware-fdm-uninstall.sh /tmp
chmod +x /tmp/VMware-fdm-uninstall.sh
/tmp/VMware-fdm-uninstall.sh

vmware-fdm-uninstall

  • reboot the host

Now you can re-add the host to the cluster and perform the upgrade to ESXi 5.5. Do not forget to enable HA again…

6 Comments

  1. Nizam

    Thanks, the second option resolved our issue,

  2. Nuno Silva

    Thank you very much! The second option also solved our problem!!

  3. rami

    Second option is working fine .Do you thing such setting has no impact on cluster configuration?

    Thanks

  4. Dhanush

    This was amazing it helped me to resolve the issue for my customer

  5. Jason Smith

    Just a note, this worked for me upgrading from 5.5u3 to 6.0u2. However I had to uninstall the FDM, NOT reboot the host, and then remediate. Hope that helps anyone on this thread that might still be experiencing the issue.

  6. forbsy

    This sure helped me. Thanks!

Leave a Comment

Your email address will not be published. Required fields are marked *