VMware Cloud Community
piedthepiper
Contributor
Contributor

vSphere C# Client ServiceInstance.RetrieveContent Intermittent Error after upgrading to v6U1

Hi Guys,

So after testing the upgrade to v6u1 (VC is 6.0.0 Build 3018524) from 5.1 I have come across this error, it is intermittent. After a couple of goes I eventually can log in.

It doesn't matter if I am using AD or SSO logins, the issue is the same.

It even has the same issue if I try to use the client to log into a host directly.

This to me seems odd, very odd. I never noticed the issue till after upgrading to 6.0u1

Log for vSphere Client Launcher, pid=1716, version=6.0.0, build=build-3016447, option=release

[        :QuickInf:W: 6] 2016-01-05 17:01:15.512  Set the dll search path to C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\6.0

[        :QuickInf:W: 6] 2016-01-05 17:01:15.777  Load Shared DLLs: C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\6.0

[        :startup :W: 6] 2016-01-05 17:01:16.026  Log for vSphere Client, pid=1716, version=6.0.0, build=build-3016447, option=release, user=xxxx\xxxx, url = https://vc.production./sdk

[viclient:SoapTran:W: 6] 2016-01-05 17:01:16.775  Invoke 1 Start RetrieveContent on ServiceInstance:ServiceInstance [mnabvmwvc.production.mnautuk.com]. [operationID:C44F26C0-00000001][Caller: VmomiSupport.VcServiceImpl.InitializeTransport]

[viclient:SrvMsg  :W: 6] 2016-01-05 17:01:18.741  RMI Request Vmomi.ServiceInstance.RetrieveContent - 1

[viclient:Critical:P:14] 2016-01-05 17:01:49.001  Connection State[vc.production]: Connected

[viclient:SoapTran:W: 6] 2016-01-05 17:01:49.016  Invoke 1 Finish RetrieveContent on ServiceInstance:ServiceInstance [vc.production] - Serial:1.949, Server:030.249 [ERROR]

VirtualInfrastructure.Exceptions.RequestTimedOut: The request failed because the remote server 'vc.production' 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.

Exactly the same error regardless of login and regardless of whether I try vCenter or to a host. (this would lead me to believe it is not a vSphere issue, as logging into a host with root bypasses vSphere). I can SSH into hosts fine with no issue.

The testing environment, is running on an isolated vSwitch, with clones of the production DCs and restores of the vSphere VMs done with Veeam. The vSwitch has promis/mac/forged tans = accept.

I have windows vms acting as routers between the isolated networks, so it is as close to my prod environment as I could get, I am unsure if this is an issue isolated to something in this test scenarios or if its an issue that will happen during live.

The web client works flawlessly, I can log in with any account quickly with no issue at all.

I have a call logged with VMware support to, as I dont really want to upgrade my prod environment while I dont have a solid idea about what is causing this issue.

When I am logged into the Windows vCenter VM, and use the client in that VM, I can login fine to everywhere, I haave read that it could be MTu related, if so why would it suddnely start now and the vSwitch is set to 1500 by default and it has no external uplinks attached

I have restored my 5.1 test environment and I am going to try again

I am open to any ideas!


Cheers

Reply
0 Kudos
2 Replies
piedthepiper
Contributor
Contributor

I have rolled back the environment and upgraded again. the upgrade is faultless, I uninstalled all previous versions of the client and just installed the v6 client. But the issue still persists, after a couple of attempts it goes in fine and works as normal.

The web client is not impacted at all and works flawlessly

Reply
0 Kudos
xmy2016
Contributor
Contributor

Hi,

     I installed vCenter server 6 today ,and I can't login in with administrator@vsphere.local for the first time wether use web client or the client .The vsphere web client occured weith an error ,but the vmware vsphere web client service run well.It still after I restart the service. I found some answers on the Internet ,didn't work……

Reply
0 Kudos