vSphere Installation Error 1603

When installing vSphere client from ESXi server you can encounter an error:

The Microsoft .NET Framework 3.0 SP1 installer return code ‘1603’.

That’s what VMware site tells about that:

vSphere Client installation might fail with Error 1603 if you do not have an active Internet connection:

You can install the vSphere Client in two ways: from the vCenter Server media or by clicking a link on the ESX, ESXi, or vCenter Server Welcome screen. The installer on the vCenter Server media (.iso file or .zip file) is self-contained, including a full .NET installer in addition to the vSphere Client installer. The installer called through the Welcome screen includes a vSphere Client installer that makes a call to the Web to get .NET installer components.

If you do not have an Internet connection, the second vSphere Client installation method will fail with Error 1603 unless you already have .NET 3.0 SP1 installed on your system.

Workaround: Establish an Internet connection before attempting the download, install the vSphere Client from the vCenter Server media, or install .NET 3.0 SP1 before clicking the link on the Welcome screen.

In my case I had restricting rule on proxy server which didn’t allow me to access Microsoft site for automatic .NET download. But loosening restrictions didn’t solve the issue. I installed Framework .NET manually version 3.5 SP1.

Tags: .NET, ESXi, firewall, framework, Microsoft, proxy, vSphere

This entry was posted on October 18, 2011 at 5:23 am and is filed under Virtualization. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Niktips's Blog