VMware Cloud Community
jokken1
Contributor
Contributor

vcenter 6.5 windows 2012R2 server can no longer get to the vsphere webclient webpage.

hi,

I have a vcenter 6.5 windows 2012R2 server. I can no longer get to the vsphere webclient webpage.

usually I go to https://vcenter.mydomain.com:9443/vsphere-client

I was getting error "503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::NamedPipeServiceSpec"

when going to https://vcenter.mydomain.com:9443/vsphere-client url

but now i get nothing: Unable to connect (via chrome and firefox)

We are going thru a company transition here and I believe the administrator account on this server has had its name changed, and its password changed. Although I don't know if that account was used to set up SSO or not... or if SSO is even any part of the issue.

I don't know very much about vcenter but inherited this issue. i don't know where to start to check all the needed services and their status. I do see all vmware services are started in the windows Services console.

i don't know where to start please give me some pointers!

thanks!

0 Kudos
6 Replies
daphnissov
Immortal
Immortal

This might seem like a punt, but if you're not that familiar with vCenter and you have active SnS, I would probably recommend you get a support case opened with VMware so they can lead you through the troubleshooting process. As a result, you're likely to learn a great deal about some of the inner workings of the software.

0 Kudos
msripada
Virtuoso
Virtuoso

One thing on windows needs to be verified is user accounts permissions .. below is the KB

VMware Knowledge Base

Please go to the vCenter via RDP -> Open command prompt as administrator

change directory to below location

cd c:\program files\vmware\vCenterserver\bin

service-control --status --all

Please share the output of the above command.

Thanks,

MS

0 Kudos
jokken1
Contributor
Contributor

thank you for your responses.

I'll will probably end up calling like you suggest daphnissov

msripada, here is the output, thank you

C:\Program Files\VMware\vCenter Server\bin>service-control --status --all

Running:

EsxAgentManager VMWareAfdService VMWareCertificateService VMWareDirectoryServic

e VMwareDNSService VMwareIdentityMgmtService VMwareSTS rhttpproxy vPostgres vmon

vmware-cis-config vmware-license vmware-psc-client

Stopped:

VMWareCAMService VMwareComponentManager VServiceManager content-library mbcs

vapiEndpoint vimPBSM vmonapi vmsyslogcollector vmware-autodeploy-waiter

vmware-imagebuilder vmware-network-coredump vmware-perfcharts vmwareServiceControlAgent

vpxd vpxd-svcs vsan-health vsphere-ui vspherewebclientsvc

0 Kudos
msripada
Virtuoso
Virtuoso

component manager failed to start .. please check cm.log

Thanks,

MS

0 Kudos
jokken1
Contributor
Contributor

thanks msripada,

i see an error in cm.log

2018-05-04T16:06:43.746-04:00 [pool-14-thread-2  DEBUG com.vmware.vim.vmomi.client.http.impl.ThumbprintTrustManager (49adee79-d7e9-46a9-a059-6726ef105f09)] Server certificate assertion verified

2018-05-04T16:06:54.473-04:00 [pool-1-thread-1  INFO  com.vmware.identity.token.impl.SamlTokenImpl (e2d03c83-1d82-40dd-afca-4a3e5980bcdd)] SAML token for SubjectNameId [value=vpxd-423128d0-a34f-11e5-a4fa-52540084b8a5@vsphere.local, format=http://schemas.xmlsoap.org/claims/UPN] successfully parsed from Element

2018-05-04T16:06:54.479-04:00 [pool-1-thread-1  INFO  com.vmware.cis.services.common.sso.LoginHelper (e2d03c83-1d82-40dd-afca-4a3e5980bcdd)] loginByToken: Successfully authenticated 'vpxd-423128d0-a34f-11e5-a4fa-52540084b8a5@vsphere.local' on session f9539782-b7ab-4fde-8cda-12859524e89a

2018-05-04T16:06:54.490-04:00 [pool-6-thread-1  ERROR com.vmware.vim.vmomi.server.impl.DispatcherImpl ()] Internal server error during dispatch

(vmodl.fault.InvalidRequest) {

   faultCause = null,

   faultMessage = null

}

at com.vmware.vim.vmomi.server.impl.DispatcherImpl$SingleRequestDispatcher.translateToInvalidRequest(DispatcherImpl.java:433)

at com.vmware.vim.vmomi.server.impl.DispatcherImpl$SingleRequestDispatcher.dispatch(DispatcherImpl.java:265)

at com.vmware.vim.vmomi.server.impl.DispatcherImpl.dispatch(DispatcherImpl.java:229)

at com.vmware.vim.vmomi.server.http.impl.CorrelationDispatcherTask.run(CorrelationDispatcherTask.java:58)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

2018-05-04T16:06:54.491-04:00 [pool-6-thread-1  WARN  com.vmware.vim.vmomi.server.impl.DispatcherImpl ()] Error getting body handler for request with soap-action null: Request method namespace 'null' is not supported. Using default non-internal namespace to marshal the response now.

2018-05-04T16:06:54.498-04:00 [pool-14-thread-3  INFO  com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider (7d067868-614a-4826-91ad-3623bfcf0b39)] Site affinity is disabled

2018-05-04T16:06:54.529-04:00 [pool-1-thread-1  INFO  com.vmware.cis.services.common.sso.LoginHelper (6957f44b-9fb4-4b1a-b804-5aadbb9a93f2)] logout: Closing session 'f9539782-b7ab-4fde-8cda-12859524e89a' for 'vpxd-423128d0-a34f-11e5-a4fa-52540084b8a5@vsphere.local'

2018-05-04T16:11:43.819-04:00 [pool-14-thread-4  INFO  com.vmware.vim.lookup.client.SiteAffinityServerEndpointProvider (2e40cbb9-8f28-4861-ad55-f03106889d73)] Site affinity is disabled

2018-05-04T16:11:43.847-04:00 [pool-14-thread-4  DEBUG com.vmware.vim.vmomi.client.http.impl.ThumbprintTrustManager (2e40cbb9-8f28-4861-ad55-f03106889d73)] Server certificate chain is trusted

2018-05-04T16:11:43.847-04:00 [pool-14-thread-4  DEBUG com.vmware.vim.vmomi.client.http.impl.ThumbprintTrustManager (2e40cbb9-8f28-4861-ad55-f03106889d73)] Server certificate chain is trusted

2018-05-04T16:11:43.854-04:00 [pool-14-thread-4  DEBUG com.vmware.vim.vmomi.client.http.impl.ThumbprintTrustManager (2e40cbb9-8f28-4861-ad55-f03106889d73)] Server certificate assertion verified

2018-05-04T16:11:43.854-04:00 [pool-14-thread-4  DEBUG com.vmware.vim.vmomi.client.http.impl.ThumbprintTrustManager (2e40cbb9-8f28-4861-ad55-f03106889d73)] Server certificate assertion verified

0 Kudos
msripada
Virtuoso
Virtuoso

This looks normal. I am unsure why the cm service showing as stopped.. Can you reboot the vCenter or stop all the services and start all the services. check which service failed to start

Thanks,

MS

0 Kudos