Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Vmware ESX - Licensing bug in Vi 3.5 Update 2 - A general system error occurred

  • 12-08-2008 1:33pm
    #1
    Registered Users, Registered Users 2 Posts: 10,288 ✭✭✭✭


    It’s date related. Apparently, a Vi3 system can become unlicensed after an upgrade to U2…

    http://communities.vmware.com/thread/162377?tstart=0
    Starting this morning, we could not power on nor VMotion any of our Virtual Machines. The VI Client threw the error “A general system error occurred: Internal Error”.
    Further digging lead us to messages like this one in /var/log/vmware/hostd.log, and the log file for any virtual machine we tried to power on or VMotion:
    Aug 12 10:40:10.792: vmx| http://msg.License.product.expired This product has expired.
    Aug 12 10:40:10.792: vmx| Be sure that your host machine’s date and time are set correctly.
    Aug 12 10:40:10.792: vmx| There is a more recent version available at the VMware Web site: “
    http://www.vmware.com/info?id=4“.

    Hold off on the upgrade for a while. If you've already applied it, do NOT reboot any of the hosts or they will not fire up again.

    Bad times for VMware


Comments

  • Registered Users, Registered Users 2 Posts: 811 ✭✭✭Rambo


    The_Edge wrote: »
    It’s date related. Apparently, a Vi3 system can become unlicensed after an upgrade to U2…

    http://communities.vmware.com/thread/162377?tstart=0



    Hold off on the upgrade for a while. If you've already applied it, do NOT reboot any of the hosts or they will not fire up again.

    Bad times for VMware

    Thanks for the warning


  • Registered Users, Registered Users 2 Posts: 10,288 ✭✭✭✭Standard Toaster


    vmware_logo_newsletter.gifheader_right_newsletter.giftable_blue_up.gif ESX/ESXi 3.5 Update 2 table_blue_down.gif
    Dear VMware Customers,
    We have released the express patches for the product expiration issue. Please go to http://www.vmware.com/go/esxexpresspatches for download and KB articles. Since our last customer email we have completed our verification tests that the express patches we’ve released are fully compatible with the VMware Update Manager. Please see the KB articles for deployment information regarding Update Manager.
    The KB articles are kept up-to-date. Please refer to the KB articles for information and updates.
    In our last update, we referred to an initiative by our support and engineering teams to find an option to apply the patch without the necessity of entering maintenance mode and VMotion of VM’s to other servers, or VM power-off and re-power-on. Our earlier tests have not found a consistently successful way to address this. We continue to investigate this possibility, as we know that it would reduce the maintenance burden on our customers who may not have a patched server available for VMotion.
    We are on target to release updated versions of the ESX/ESXi 3.5 Update 2 patch at 6 PM PST today. This is for customers who have not already upgraded to the previously released version of ESX/ESXi 3.5 Update 2
    Thank you,
    The VMware ESX Product Team
    Problem:
    An issue has been discovered by many VMware customers and partners with ESX Update 2 (build number 103909) and ESXi 3.5 Update 2 (build number 103908) where Virtual Machines fail to power on or VMotion successfully. This problem began to occur on August 12, 2008 for customers that had upgraded to ESX 3.5 Update 2. The problem is caused by a build timeout that was mistakenly left enabled for the release build.
    The following message is displayed in the vmware.log file for the virtual machine:
    This product has expired. Be sure that your host machine's date and time are set correctly.

    Module License Power on failed.
    Affected Products:
    - VMware ESX 3.5 Update 2 & ESXi 3.5 Update 2. Thank you, The VMware ESX Product Team
    - The problem will be seen if ESX350-200806201-UG is applied to a system.
    - No other VMware products are affected.
    Resolution:
    VMware Engineering has produced express patches for impacted customers to resolve the issue.



    ========================================================================


    xpress Patch Download

    Special Notice: Please Read

    An issue has been uncovered with ESX/ESXi 3.5 Update 2 that causes the product license to expire on August 12, 2008.

    Follow the steps below to correct this issue:
    1. Read the following Knowledge Base articles first:
      • Fix of virtual machine power on failure issue, refer to KB 1006716
      • For VI 3.5, refer to KB 1006721 for deployment consideration and instruction
      • For VI3.5i, refer to KB 1006670 for deployment consideration and instruction
    2. Download and apply the express patch according to the product(s) you have:


Advertisement