CustomAction VM_InstallJRE returned actual error code 1624

vCenter Server 5.5 Update 2e contains fix of Storage Monitor Service. It’s also a stable version since 5.5 Update 1. I got a problem when I upgraded my development vCenter Server last weekend. I’d like to share the solution since VMware doesn’t document that problem. (Maybe I didn’t find it. :-)) It’s kind tricky.

vCenter Server 5.5 Update 2e包含SMS服务的bug修复,它也是当前比较稳定的版本。上周我在升级vCenter Server到这个版本时遇到了一个问题。此问题不是那么容易修复因为VMware的KB并没有提供解决方案,我在这里把我的方法共享出来。

The upgrading failed during SSO server stage. First time it ran around 10 minutes then failed at JRE installation, second time it failed in second. I found following events in installation logs:

CustomAction VM_InstallJRE returned actual error code 1624

Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected.

It indicates something happened when updating JRE. I searched the error code and found it related to MSI install source. Looks like vCenter Server had a bad installer source of JRE. To fix this problem you have to open register editor and go to HKEY_LOCAL_MACHINESOFTWAREClassesInstallerProducts, double-click Transforms key and remove the value.

This problem usually appears on Windows Server 2008 vCenter Server when you delete temp files on %temp% before upgrading. You will get other two or three failures on SSO components after fix this, just repeat the steps above.

Once all components upgraded, installer will again asks you choose current SSO installer executable file of vCenter Server. You must select installer file of installed SSO server currently. If you don’t know the server, go to check vpxa.log to find vCenter Server version, then go to my.vmware.com to download proper ISO and extract the SSO installer.

Location of SSO Server installation file

Location of SSO Server installation file

Chinese Version

 

Advertisements

2 thoughts on “CustomAction VM_InstallJRE returned actual error code 1624

  1. Neal

    Good find, this one had me banging my head against the wall all morning. Thanks for posting! Mine happened on a vCenter Server running 2012 (non R2).

    Reply
    1. Wu Post author

      Thank you. I’m glad to help. BTW, I recommend use Windows 2012R2 with rollup 5. Pretty stable.

      Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s