Troubleshooting a failed vSphere/Virtual Infrastructure Client installation
book
Article ID: 311648
calendar_today
Updated On:
Products
VMware vCenter ServerVMware vSphere ESXi
Issue/Introduction
This article provides steps to troubleshoot a failed vSphere/VI Client installation.
Symptoms:
You cannot install the vSphere/Virtual Infrastructure (VI) Client.
Installing the vSphere/VI Client fails.
The vSphere/VI Client installation fails to complete.
You may see one or more of these errors during the vSphere/VI Client installation:
Error 1603
The Microsoft Visual J# 2.0 second edition installer returned error code 4113
Microsoft Visual J# 2.0 Second edition installer returned error code '2147942406' Error creating process <install /q /l>. Reason: The handle is invalid.
Plugin Installer Error: Unable to connect to the remote server.
Login Failed
Setup failed to launch <path of the VMware-VIClient executable file>
Setup has detected that the Microsoft .NET Framework 2.0 pre-requisite is not installed on this system. Please install this pre-requisite and try again.
Validate that each troubleshooting step below is true for your environment. Each step will provide instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.
File a support request with VMware Support and quote this Knowledge Base article ID (1037551) in the problem description. For more information, see How to Submit a Support Request.
Additional Information
Starting with vSphere 5.1, the vSphere Infrastructure Client is deprecated and is replaced with the vSphere Web Client.
You can get more troubleshooting information from these logs:
Pre-Windows 2008 – C:\Documents and Settings\Local Settings\Temp
Windows 2008 and Windows 7 – C:\Users\user>\AppData\Local\Temp vminst.log vim-vic-msi.log