vSphere Web Client is missing VMware Lookup Service configuration

[Pcyber]

Hi, I have a problem.

I have virtual enviroment with three host Vmware 5.5 Update 2 and vCenter Windows 2008R2. When I try connect to Web client at https://xxx.xxx.xxx.xxx.:9443/vsphere-client/  and connect it I recceived ane error:

"vSphere Web Client is missing VMware Lookup Service configuration"

Any suggest?

Thanks

[vijayrana968]

Can you check in service.msc that VMware lookup and other services are running fine ? Alos check logs under C:\ProgramData\VMware\vSphere Web Client\serviceability\

[Pcyber]

I checked services and it's ok.

This is the last part of the C:\ProgramData\VMWare\vSphere Web Client\serviceability\vsphere_client_virgo.log regarding my authentication attempt:

===============================================================================================================

[2017-11-28 14:50:45.450] [INFO ] Timer-0                       com.vmware.vise.util.debug.SystemUsageMonitor                    

Heap     : init = 1073741824(1048576K) used = 409134544(399545K) committed = 1058668544(1033856K) max = 1058668544(1033856K)

non-Heap : init = 136773632(133568K) used = 97917544(95622K) committed = 171507712(167488K) max = 587202560(573440K)

No of loaded classes : 15457

Live Thread Count : 4

Peak Thread Count : 80

Daemon Thread Count : 72

[2017-11-28 14:51:57.006] [INFO ] http-bio-9443-exec-13        70001370 100040 ###### com.vmware.vise.util.i18n.I18nFilter                              The preferred locale for session 100040 is set to: it_IT

[2017-11-28 14:52:16.233] [INFO ] http-bio-9443-exec-13        70001418 ###### ###### com.vmware.vise.security.SessionListener                          Session 100041 created with context path: /vsphere-client/endpoints

[2017-11-28 14:52:16.234] [INFO ] http-bio-9443-exec-13        70001418 ###### ###### org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint secure-amf received request.

[2017-11-28 14:52:16.280] [INFO ] http-bio-9443-exec-13        70001419 100041 ###### org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint secure-amf received request.

[2017-11-28 14:52:16.723] [INFO ] http-bio-9443-exec-14        70001420 100041 ###### org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint secure-amf received request.

[2017-11-28 14:52:16.744] [INFO ] http-bio-9443-exec-13        70001421 100040 ###### org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint secure-amf received request.

[2017-11-28 14:52:16.825] [INFO ] http-bio-9443-exec-13        70001422 100040 ###### org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint secure-amf received request.

[2017-11-28 14:52:16.826] [INFO ] http-bio-9443-exec-13        70001422 100040 ###### c.vmware.vsphere.client.usersession.impl.UserSessionServiceImpl   getUserSession called on an inactive session.

[2017-11-28 14:52:17.334] [INFO ] http-bio-9443-exec-14        70001424 100041 ###### org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint secure-amf received request.

[2017-11-28 14:52:17.336] [INFO ] http-bio-9443-exec-13        70001423 100040 ###### org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint secure-amf received request.

[2017-11-28 14:52:26.992] [INFO ] http-bio-9443-exec-13        70001425 100040 ###### com.vmware.vise.util.i18n.I18nFilter                              The preferred locale for session 100040 is set to: it_IT

[2017-11-28 14:52:26.993] [INFO ] http-bio-9443-exec-13        70001425 100040 ###### com.vmware.vise.security.DefaultAuthenticationProvider            Authenticating user: (UtentePersonale) using authentication handler: com.vmware.vsphere.client.security.sso.SsoAuthenticationHandler@75914941

[2017-11-28 14:55:45.450] [INFO ] Timer-0                       com.vmware.vise.util.debug.SystemUsageMonitor                    

Heap     : init = 1073741824(1048576K) used = 423730536(413799K) committed = 1058668544(1033856K) max = 1058668544(1033856K)

non-Heap : init = 136773632(133568K) used = 97920160(95625K) committed = 171507712(167488K) max = 587202560(573440K)

No of loaded classes : 15457

Live Thread Count : 4

Peak Thread Count : 80

Daemon Thread Count : 72

[2017-11-28 15:00:45.451] [INFO ] Timer-0                       com.vmware.vise.util.debug.SystemUsageMonitor                    

Heap     : init = 1073741824(1048576K) used = 423731496(413800K) committed = 1058668544(1033856K) max = 1058668544(1033856K)

non-Heap : init = 136773632(133568K) used = 97920160(95625K) committed = 171507712(167488K) max = 587202560(573440K)

No of loaded classes : 15457

Live Thread Count : 4

Peak Thread Count : 80

Daemon Thread Count : 72

[2017-11-28 15:05:45.451] [INFO ] Timer-0                       com.vmware.vise.util.debug.SystemUsageMonitor                    

Heap     : init = 1073741824(1048576K) used = 423732456(413801K) committed = 1058668544(1033856K) max = 1058668544(1033856K)

non-Heap : init = 136773632(133568K) used = 97920160(95625K) committed = 171507712(167488K) max = 587202560(573440K)

No of loaded classes : 15457

Live Thread Count : 4

Peak Thread Count : 80

Daemon Thread Count : 72

====================================================================================================================

Any suggest?

[msripada]

Can you check if the webclient is registered with SSO using the list service command from the below KB?

VMware Knowledge Base

Is the webclient installed on the same vCenter server or different location (drive or different machine)?

[Pcyber]

This is the report that you asked me.

Intializing registration provider...

Getting SSL certificates for https://mioserver.miodominio.local:7444/lookupservic

e/sdk

Anonymous execution

Found 6 services.

Service 1

-----------

serviceId=Default-First-Site:614c3f19-cb4d-48f1-92c8-4daa424e12cd

serviceName=vCenterService

type=urn:vc

endpoints={[url=https://mioserver.miodominio.local:443/sdk,protocol=vmomi]}

version=5.1

description=vCenter Server

ownerId=vCenterServer_2014.02.05_124908@System-Domain

productId=

viSite=Default-First-Site

Service 2

-----------

serviceId=Default-First-Site:522bf5b8-e903-48e1-850a-d121b940d2c5

serviceName=The group check interface of the SSO server

type=urn:sso:groupcheck

endpoints={[url=https://mioserver.miodominio.local:7444/sso-adminserver/sdk/vsphe

re.local,protocol=vmomi]}

version=1.5

description=The group check interface of the SSO server

ownerId=

productId=product:sso

viSite=Default-First-Site

Service 3

-----------

serviceId=Default-First-Site:0066d92c-c6c4-4d8d-98dc-6069104c7234

serviceName=The administrative interface of the SSO server

type=urn:sso:admin

endpoints={[url=https://mioserver.miodominio.local:7444/sso-adminserver/sdk/vsphe

re.local,protocol=vmomi]}

version=1.5

description=The administrative interface of the SSO server

ownerId=

productId=product:sso

viSite=Default-First-Site

Service 4

-----------

serviceId=Default-First-Site:f537bdf8-fa0c-46c0-8414-829b94d49dde

serviceName=VMware vSphere Web Client

type=urn:com.vmware.vsphere.client

endpoints={[url=https://vserver1:9443/vsphere-client,protocol=vmomi]}

version=5.1

description=VMware vSphere Web Client Service

ownerId=WebClient_2014.02.05_123436

productId=

viSite=Default-First-Site

Service 5

-----------

serviceId=Default-First-Site:0badf239-3f3b-4bb4-85f8-b5e4daf2d8b3

serviceName=The security token service interface of the SSO server

type=urn:sso:sts

endpoints={[url=https://mioserver.miodominio.local:7444/sts/STSService/vsphere.lo

cal,protocol=wsTrust]}

version=1.5

description=The security token service interface of the SSO server

ownerId=

productId=product:sso

viSite=Default-First-Site

Service 6

-----------

serviceId=Default-First-Site:950bc6db-95cc-44d0-9112-20a84eada5a2

serviceName=VMware Log Browser

type=urn:logbrowser:logbrowser

endpoints={[url=https://vserver1:12443/vmwb/logbrowser,protocol=unknown],[url=ht

tps://vserver1:12443/authentication/authtoken,protocol=unknown]}

version=1.0.1441089

description=Enables browsing vSphere log files within the VMware Web Client

ownerId=WebClient_2014.02.05_123436

productId=

viSite=Default-First-Site

Return code is: Success

0

[Pcyber]

Any suggest?

[SureshKumarMuth]

I can see the webclient is registered with SSO

Service 4

-----------

serviceId=Default-First-Site:f537bdf8-fa0c-46c0-8414-829b94d49dde

serviceName=VMware vSphere Web Client

type=urn:com.vmware.vsphere.client

endpoints={[url=https://vserver1:9443/vsphere-client,protocol=vmomi]}

version=5.1

description=VMware vSphere Web Client Service

ownerId=WebClient_2014.02.05_123436

productId=

viSite=Default-First-Site

However ,there is some issue between SSO and webclient. Is webclient is allowing you to enter the credentials ? Can you use Administrator@vsphere.local to login and check SSO administration page for solution users ?

Or simple way to resolve this is, take a snapshot of your webclient machine and reinstall the webclient, point it to SSO again, this will help you to eliminate the SSO- Webclient connectivity issue. If anything goes wrong you can always revert the snapshot.