Getting quite desperate here... I'm trying to self-study vSphere, based on a setup of version 5.5 in VMWare Workstation 9. This all on my quadcore 16GB RAM laptop. And after two days of struggling, I can't even get started because a plain simple setup doesn't work!
The error I get stuck on each time happens during the Web Client installation:
1152: Error extracting C:\Users\Administrator\AppData\Local\Temp\{378E4D59-A095-46BC-BB1B-A1BCF7013AC5}\vSphere Webclient.msi to the temporary location
Actually, I first notice it when the "Simple Install" stops after successfull SSO installation and warns that I have to install the other components manually. When I do so with the Web Client, I can see the InstallShield Wizard extract it seemingly successfully, creating the random-looking subfolder with an MST, some configuration files, and "VMWare vSphere Web Client.exe". Then, a "decompressing" phase starts that gets to about 75% then gives the error.
- first time this happened on a Win2008 R2 VM that I had installed from a template
- I next tried on a freshly installed Win2012 RTM VM, same problem
- next tried on a Win2012 R2 RTM, here things end in another problem (mentioned in another forum, some file missing on 2012R2 and having to install LDS manually, but 2012R2 "not supported" so I'm not going to try this)
BUT! : when I start a manual installation of the Web Client on 2012 R2, the "1152 Error extracting" DOESN'T happen, it goes successfully past "decompressing"!!! So I thought I was going to be smart and just copy the decompressed folder to the other server. Alas, when trying to launch the install from these files you get a message that it only works when the vCenter Installer initializes the installation... So that is back to square 1
The vCenter Installer handles all the stages in one "transaction" and I don't think you can tell it you have prepared a subfolder with decompressed "VMWare vSphere Web Client.exe"
- next, I figured since the decompression worked on 2012 R2 but not on my 2012, it had to be some essential Windows Update that had been published between 2012 RTM and 2012R2 and that affected Windows Installer. So I downloaded 600+ MB of updates to the 2012 RTM server, installed to get it 100% up-to-date (took a couple of hours).
Result: no difference...
Other things I tried: installing under local administrator (figuring that the path of the temp folder could have something to do), installing under Safe Mode (not possible since Windows Installer not available), increasing VM memory to an insane 13GB (against 4GB), running via "run as administrator", run via "Troubleshoot compatibility", choosing another setup language in the drop-down box when you start the installation...
I have obviously also re-downloaded the 3.3 GB iso file, but this didn't make a difference. And I would think the decompression would also cause an error on 2012R2 then as well, if this part was corrupt.
I'm totally out of ideas now.. Figured I better tried to download and evaluate another version maybe. Hope somebody has other suggestions.
TIA
Hello and welcome to the communities.
Might be asking the obvious here, but did you verify the checksums of that download to make sure it was not corrupt?
Hello and welcome to the communities.
Might be asking the obvious here, but did you verify the checksums of that download to make sure it was not corrupt?
Bull's eye ![]()
I didn't even need you to point out.. Almost right after posting the message I went to check out whether I couldn't download another version, so I noticed the checksums. I had seen them before, but the fact that the decompressing went correct on the 2012R2 installation, and the fact that I already downloaded the ISO a second time, had taken me on another path.
The checksum was indeed different... So I downloaded again and a first test seems to confirm it will be OK now (didn't have time to do a complete reinstall yet).
Still not sure what happened there??? Did I accidentally mix up files, and used the correct copy on 2012R2 and the corrupt one on the others? Was the copy on the VMware servers corrupt for a couple of hours? Did my second download pick up a copy of the downloaded corrupt version that was cached somewhere on the interwebs??
Now that I'm back here anyway: is it reasonably feasible to set up a virtual vSphere 5.5.0a testlab on a 16GB RAM laptop? The requirements are quite steep. I'd like to test 2 clustered ESXi, one server with all the "Simple Install" components, and maybe iSCSI storage on a 2012 or 2008R2 with iSCSI target. Then I possibly also have to have my domain DC running? Are the minimum requirements absolute? ESXi mentions 4GB, the vCenter Server 12 (? that can't be serious I bet, I hope it's 4 also??).That would make 12, and at least 1GB for the iSCSI target server and the DC, each. Doesn't leave much spare... Would using 2008R2 systems be lighter on resources than 2012 (the only reason I went 2012 was the initial problems with the corrupt ISO)?
Jhel
Haha, yes - 16GB will absolutely get it done!
Here is what I have on a IBM T430 laptop with i7, SSD, 16GB RAM and Windows 8 and Workstation 9:
Windows 2003 DC - 1 vCPU, 256GB RAM
Windows 2008 R2 Starwind iSCSI Target - 1 vCPU, 1GB RAM
Windows 2008 R2 vCenter Server (all components, including SQL Express) - 2 vCPUs, 4GB RAM
ESXi 5.5 #1 - 2 vCPUs, 4GB RAM
ESXi 5.5 #2 - 2 vCPUs, 4GB RAM
Windows 2008 R2 with SQL 2008 R2 - 2 vCPUs, 2GB RAM
Its sometimes slow and I can't power up really useful VMs under the ESXi hosts, but it works extremely well for learning/testing. You will be fine to throttle some of those back.
I've got it up and running with the systems I mentioned in my previous post! Didn't use any "nested" VMs yet, though, lol.
The web client is a paaaaaaaaain in this setup. I almost fall asleep between screen refreshes. ![]()
I just discovered that the "normal" vCenter Client can also be used. Installed it on the vCenter Server system and I think I'll use that one for a while at least in the beginning, even though it doesn't support the newest features. The amount of time I lose when I use the WEB client to browse through the infrastructure to get a feel for things was starting to add up rapidly.
Jhel
Unfortunately, that Web Client slowness can be expected in these low memory situations. The vSphere Web Client system requirements alone call for 2GB RAM.
I have this issue too. But I've downloaded for twice, but still, the same error occurred. What should I do now? It's been two days elapsed and not even a little progress. The vSphere Web Client just can't be installed at all. Give a hand
I faced this error too. Please try to use ova file. It's work!!!!
!
