$theTitle=wp_title(" - ", false); if($theTitle != "") { ?>
About Virtualization, VDI, SBC, Application Compatibility and anything else I feel like
Today I connected with my laptop to VMWare Virtual Center using vSphere client. Because I had an older version of the client I needed to update and the installer failed with this message:
I remembered this error from the last install of this client (about a year ago), it happens because Microsoft Visual J# was already installed (in my case it was previously installed by Embarcadero’s Rad Studio).
Last year I “fixed” it by modifying the msi file but I remembered that Assarbad posted an easier solution on his Blog a while ago.
His solution was to set a public property in the MSI (USING_VIM_INSTALLER) but it means we need to unpack the installer exe first to obtain the MSI file.
I figured there might be a way to pass this property directly to the installer. Launching the installer with /? as argument which shows us the possible Command line parameters:
Seems like /V is what we need and after trying several variations the correct one is:
VMware-viclient.exe /V”USING_VIM_INSTALLER=1″
Note there must not be a space between /V and “USING_VIM_INSTALLER=1”.
And then finally it works!
6 Responses for "The case of the VMware vSphere Client"
[…] The case of the VMware vSphere Client VN:F [1.9.5_1105]please wait…Rating: 0.0/10 (0 votes cast)VN:F [1.9.5_1105]Rating: 0 (from 0 […]
seriously you are a lifesaver!!!! Thanks u worked perfectly!
@Joe: Glad it helped and let’s hope VMWare fixes this silly thing.
VMware vSphere client 4.1 installation woes…
Trying to install vSphere client 4.1 on my private machine failed (with error 4113) the first times. It turned out the problem was the “Microsoft Visual J# 2.0 Redistributable Package” was already on my system as part of Embarcadero RAD Stu…
Had the same problem on win7 x64
Did the following:
1) VMware-viclient.exe /dc:\temp\vmclient\ /x
2) C:\Temp\vmclient\bin\VMware-viclient.exe /vUSING_VIM_INSTALLER=1
Worked 🙂
Thanks for your tip! 🙂
I’m having the same issue installing Vmware Vpshere client 5.0 on CentOS 6.3. Though I am getting the same error, but code 4122. I tried running that code, but it claims to not have that file, even when I navigate to the folder it is clearly in.
Leave a reply