The command has timed out as the remote server is taking too long to respond. (The command has timed out as the remote server is taking too long to respond.) The request failed because the remote server 'xxxxx' took too long to respond. Just for the sake of it, here’s the error log: 10:12:35.520 RMI Error - 4 Here’s the VMware KB article about timeout values:, there’s also instructions on how to edit the Windows registry if you can’t bring up vSphere client. Change the Client-Server Command Timeout value to Use a custom value and the Timeout in seconds to 60. changed the value to 60 seconds and it all worked fine!įire up vSphere Client and connect to another vCenter Server or ESXi host, then click Edit->Client Settings. The default timeout value is 30 seconds, and my suspicion is that the vCSA was taking slightly longer to respond to authentication…. Web Client worked fine for both, but it was the vSphere C# client that was timing out for the vCSA!Īfter much head scratching and trawlling through logs (Found at C:\Users\username\AppData\Local\VMware\vpx\viclient-x-0000.log), it turns out the problem is with the default time out value of the vSphere client for authentication.
It was a strange issue because I could log into the Windows vCenter Server I had deployed in my primary cluster, but couldn’t log into the vCenter Server Appliance I had deployed in my secondary cluster…. I’ve been upgrading my company’s solution centre to vSphere/vCenter 6.0 update 2 the past week and noticed that I was having issues logging into the vCenter Server Appliances I had deployed.
0 kommentar(er)
