Logging into vCenter Server 4.0 Update 1 with vSphere Client produces the error: Request failed due to ssl error

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• When logging into the vCenter Server 4.0 Update 1 you see the error:
  
  Request failed due to ssl error
  
  
• Unable to open the certificate file in vCenter located in:
  C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL

• The vpxd.log file on the vCenter Server contains entries similar to:
  
  
  [nyvc :SoapTran] 2009-12-15 14:15:04.008 Start Invoke 1 - ServiceInstance:ServiceInstance.RetrieveContent ... Connections: 8
  [nyvc :SoapTran] 2009-12-15 14:15:04.118 Finish Invoke 1 - Serial:0.031, Server:000.066 - ServiceInstance:ServiceInstance.RetrieveContent [ERROR]
  VirtualInfrastructure.Exceptions.ConnectionError: The request failed due to an SSL error.
  System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
  
  Note: In Windows 2003, Windows XP, and Windows 2008, the vCenter Server's vpxd.logs are located at %ALLUSERSPROFILE%\VMware\VMware VirtualCenter\Logs by default.

Environment

VMware vCenter Server 4.0.x

Resolution

The error is caused by the way an outdated plugin in the vSphere Client handles the SSL connection with the vCenter server.

You must isolate the plugin that is causing the issue.

To isolate the plugin:

1. In vSphere Client, click Plug-ins > Manage Plug-ins.
2. Right-click on a plugin and choose Disable.
3. Restart vSphere Client.
4. • If the error occurs, then the plugin you disabled is not causing the issue. Reenable the plugin by right-clicking on the plugin and choosing Enable, then repeat steps 1-3 for all other plugins.
   • If the error does not occur when you restart vSphere Client after disabling a plugin, then that plugin is causing the issue.
     
5. When you isolate the plugin that is causing the issue, upgrade the plugin on vCenter Server and reinstall it in vSphere Client.
   
   Alternatively, if you do not require the plugin, you can leave it disabled in vSphere Client.