I'm getting this error message on my laptop with vSphere Client 6.0 when I'm trying to connect ESXi Server 6.0 -> Please see below the logfile.
On other computers there are no problems with connecting the ESXi 6.0 server!
What could be the reason that I get this issue? Any ideas?
[ :startup :W: 1] 2016-09-12 16:21:30.042 Log for vSphere Client Launcher, pid=5636, version=6.0.0, build=build-2502222, option=release
[ :Error :W: 1] 2016-09-12 16:21:30.073 System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.
at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str)
at Microsoft.Win32.RegistryKey.SetValue(String name, Object value, RegistryValueKind valueKind)
at Microsoft.Win32.RegistryKey.SetValue(String name, Object value)
at VpxClient.Program.RegisterClientMimeExtension()
[ :QuickInf:W: 8] 2016-09-12 16:22:07.856 Set the dll search path to C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\6.0
[ :QuickInf:W: 8] 2016-09-12 16:22:08.293 Load Shared DLLs: C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\6.0
[ :startup :W: 8] 2016-09-12 16:22:08.683 Log for vSphere Client, pid=5636, version=6.0.0, build=build-2502222, option=release, user=admin, url = https://192.168.188.10/sdk
[viclient:SoapTran:W: 8] 2016-09-12 16:22:09.447 Invoke 1 Start RetrieveContent on ServiceInstance:ServiceInstance [192.168.188.10]. [operationID:40A62C41-00000001][Caller: VmomiSupport.VcServiceImpl.InitializeTransport]
[viclient:SrvMsg :W: 8] 2016-09-12 16:22:10.742 RMI Request Vmomi.ServiceInstance.RetrieveContent - 1
[viclient:Critical:P:13] 2016-09-12 16:22:51.879 Connection State[192.168.188.10]: Connected
[viclient:SoapTran:W: 8] 2016-09-12 16:22:51.879 Invoke 1 Finish RetrieveContent on ServiceInstance:ServiceInstance [192.168.188.10] - Serial:1.277, Server:041.129 [ERROR]
VirtualInfrastructure.Exceptions.RequestTimedOut: The request failed because the remote server '192.168.188.10' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
System.Net.WebException: The command has timed out as the remote server is taking too long to respond.
--- End of inner exception stack trace ---
at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName, Object[])
at Vmomi.ServiceInstance.RetrieveContent()
at VmomiSupport.VcServiceImpl.InitializeTransport(ConnectionSpec)
at VpxClient.UI.InitializeVimClient(Dictionary`2, String[])
at VpxClient.UI.StartUpIfNotMultiVcSecure(Dictionary`2, SecureString, String[], LoginEventHandler, String, List`1)
...
at System.Reflection.RuntimeMethodInfo.Invoke(Object, BindingFlags, Binder, Object[], CultureInfo)
at VpxClient.Login.VIClientObj.LateCall(String, Object[])
at VpxClient.Login.VIClientObj.StartUpOrGetMultiVcInfo(Dictionary`2, SecureString, String[], List`1)
at VpxClient.Login.ClientAppObject.Startup(Dictionary`2, PasswordString, RunMode)
[viclient:Error :W: 8] 2016-09-12 16:22:51.895 RMI Error Vmomi.ServiceInstance.RetrieveContent - 1
<Error type="VirtualInfrastructure.Exceptions.RequestTimedOut">
<Message>The request failed because the remote server '192.168.188.10' 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>12</FrameCount>
</StackTrace>
<MethodName>Vmomi.ServiceInstance.RetrieveContent</MethodName>
<Target type="ManagedObject">ServiceInstance:ServiceInstance [192.168.188.10]</Target>
</InvocationInfo>
<WebExceptionStatus>Timeout</WebExceptionStatus>
<SocketError>Success</SocketError>
</Error>
[ :ShowExcp:W: 8] 2016-09-12 16:22:51.895 Connection Error: The request failed because the remote server '192.168.188.10' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
VirtualInfrastructure.Exceptions.RequestTimedOut: The request failed because the remote server '192.168.188.10' 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.ServiceInstance.RetrieveContent()
at VmomiSupport.VcServiceImpl.InitializeTransport(ConnectionSpec cnxSpec)
at VpxClient.UI.InitializeVimClient(Dictionary`2 specMap, String[] arguments)
at VpxClient.UI.StartUpIfNotMultiVcSecure(Dictionary`2 specMap, SecureString password, String[] arguments, LoginEventHandler handler, String dllPath, List`1 listOfVcUrls)
System.Net.WebException: The command has timed out as the remote server is taking too long to respond.
--- End of inner exception stack trace ---
[ :QuickInf:W: 8] 2016-09-12 16:23:01.770 VIC #0 End.
[ :QuickInf:W: 8] 2016-09-12 16:23:01.770 CientAppObject.CleanUp...
[ :Critical:W: 8] 2016-09-12 16:23:01.770 ShutdownClient
[viclient:Critical:W: 8] 2016-09-12 16:23:01.770 Connection State[192.168.188.10]: Disconnected
[viclient:SoapMsg :W: 8] 2016-09-12 16:23:01.770 Attempting graceful shutdown of service ...
[viclient:SoapMsg :W: 8] 2016-09-12 16:23:01.770 Pending Invocation Count: 0
[viclient:SoapMsg :W: 8] 2016-09-12 16:23:01.770 Graceful shutdown of service: Success
[ :QuickInf:W: 8] 2016-09-12 16:23:01.785 CientAppObject.CleanUpDone...
[ :QuickInf:W: 8] 2016-09-12 16:23:01.785 Scheduling delayed unload for AppDomain VIC #0