Since the upgrade of vSphere server from version 5.0 to 5.1 some users are no longer able to login, but the vSphere web client works fine.
They get the error: The server 'xxx' took to long to respond. (The command was timed out as the remote server was taking too long to resond.)
The client log file shows this:
at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName, Object[])
at Vmomi.SessionManager.LoginBySSPI(String, String)
at VmomiSupport.VcServiceImpl.LoginBySSPI(LoginSpecInternal2)
at VmomiSupport.VcServiceImpl.Login(LoginSpec)
at VirtualInfrastructure.LoginMain.Process(BackgroundWorker, DoWorkEventArgs)
at VirtualInfrastructure.LoginWorkerImpl.Worker_DoWork(Object, DoWorkEventArgs)
...
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object)
[viclient:Error :P: 3] 2012-09-18 10:06:52.925 RMI Error Vmomi.SessionManager.LoginBySSPI - 5
<Error type="VirtualInfrastructure.Exceptions.RequestTimedOut">
<Message>The request failed because the remote server 'esxvc02' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)</Message>
<InnerException type="System.Net.WebException">
<Message>The command has timed out as the remote server is taking too long to respond.</Message>
<Status>Timeout</Status>
</InnerException>
<Title>Connection Error</Title>
<InvocationInfo type="VirtualInfrastructure.MethodInvocationInfoImpl">
<StackTrace type="System.Diagnostics.StackTrace">
<FrameCount>17</FrameCount>
</StackTrace>
<MethodName>Vmomi.SessionManager.LoginBySSPI</MethodName>
<Target type="ManagedObject">SessionManager:SessionManager [esxvc02]</Target>
<Args>
<item></item>
<item></item>
</Args>
</InvocationInfo>
<WebExceptionStatus>Timeout</WebExceptionStatus>
<SocketError>Success</SocketError>
</Error>
[viclient:Critical:M: 7] 2012-09-18 10:06:52.940 Connection State[esxvc02]: Disconnected
[viclient:SoapMsg :M: 7] 2012-09-18 10:06:52.940 Attempting graceful shutdown of service ...
[viclient:SoapMsg :M: 7] 2012-09-18 10:06:52.956 Pending Invocation Count: 0
[viclient:SoapMsg :M: 7] 2012-09-18 10:06:52.956 Graceful shutdown of service: Success
[ :Error :M: 7] 2012-09-18 10:06:52.956 Error occured during login
VirtualInfrastructure.Exceptions.LoginError: The server 'esxvc02' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
at VirtualInfrastructure.LoginMain.Process(BackgroundWorker worker, DoWorkEventArgs e)
at VirtualInfrastructure.LoginWorkerImpl.Worker_DoWork(Object sender, DoWorkEventArgs e)
...
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
VirtualInfrastructure.Exceptions.RequestTimedOut: The request failed because the remote server 'esxvc02' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
at VirtualInfrastructure.Soap.SoapServiceWrapper.DoInvokeSync(ManagedObject mo, MethodName methodName, Object[] parameters, Int32 timeoutSecs)
at VirtualInfrastructure.Soap.SoapTransport.VirtualInfrastructure.Transport.InvokeMethod(ManagedObject mo, MethodName methodName, Object[] pars)
at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName methodName, Object[] pars)
at Vmomi.SessionManager.LoginBySSPI(String base64Token, String locale)
at VmomiSupport.VcServiceImpl.LoginBySSPI(LoginSpecInternal2 loginSpec)
at VmomiSupport.VcServiceImpl.Login(LoginSpec loginSpec)
at VirtualInfrastructure.LoginMain.Process(BackgroundWorker worker, DoWorkEventArgs e)
System.Net.WebException: The command has timed out as the remote server is taking too long to respond.
In my vpxd.log file I see at the same time:
2012-09-18T10:06:53.036+02:00 [11704 error 'SoapAdapter.HTTPService'] HTTP Transaction failed on stream TCPStreamWin32(socket=TCP(fd=16104) local=127.0.0.1:8085, peer=127.0.0.1:59602) with error class Vmacore::SystemException(An established connection was aborted by the software in your host machine. )
Someone knows how to resolve this?
Thanks,
Bart