500 sso error cannot connect to the vmware component manager

Hi,

Hopefully someone might be able to point me in the right direction here, I’m a bit out of my depth….

I have a LAB setup of 3x ESXi hosts, on one of which vcenter is installed.

All the ESXi hosts were added and everything was working very well. I needed to change the IP addressing of the network the three ESXi/vcenter hosts were on. Initially there was no problem, moved form 192.168.1.x/24 to 192.168.100.x/24. Again, initially everything seemed ok.

I think the problem I am now getting, which is when trying to access vsphere web client I get ‘[500] SSO error: Cannot connect to the VMware Component Manager’, started after the VM hosting vcenter rebooted, though I can’t be certain of this.

I’ve seen posts suggesting a requirement for entries in the hosts file of the vcenter server if forward/reverse DNS isnt working, but it is. I came across another post suggesting to reset the certificates using the certificate-manager.bat command, which I’ve tried but with no luck error stays the same after services/server reboot.

I pulled the vsphere-client-virgo.log but the only thing I could see in it was an entry of: failed: Connection refused: connect

In case it helps I’ve pasted the section below;

[2017-02-15T14:16:25.874Z] [INFO ] Timer-0                      com.vmware.vise.util.debug.SystemUsageMonitor                    Summary: heap = 269.95 MB, threads = 87

Heap    : init = 134217728(131072K) used = 283060008(276425K) committed = 376438784(367616K) max = 557842432(544768K)

non-Heap : init = 2555904(2496K) used = 189541640(185099K) committed = 210223104(205296K) max = -1(-1K)

No of loaded classes: 22227

Live Thread Count(w/o the live daemon threads): 6

Peak Thread Count: 90

Daemon Thread Count: 81

Tomcat Request-Processing Threads Count: 20

Blocked threads: 0

Waiting threads: 80

Threads blocked in Data Service: 0

Threads waiting in Data Service: 0

Threads blocked in Logback: 0

Threads waiting in Logback: 0

[2017-02-15T14:21:25.911Z] [INFO ] Timer-0                      com.vmware.vise.util.debug.SystemUsageMonitor                    Summary: heap = 289.84 MB, threads = 87

Heap    : init = 134217728(131072K) used = 303914664(296791K) committed = 376438784(367616K) max = 557842432(544768K)

non-Heap : init = 2555904(2496K) used = 189541640(185099K) committed = 210223104(205296K) max = -1(-1K)

No of loaded classes: 22227

Live Thread Count(w/o the live daemon threads): 6

Peak Thread Count: 90

Daemon Thread Count: 81

Tomcat Request-Processing Threads Count: 20

Blocked threads: 0

Waiting threads: 80

Threads blocked in Data Service: 0

Threads waiting in Data Service: 0

Threads blocked in Logback: 0

Threads waiting in Logback: 0

[2017-02-15T14:23:34.228Z] [INFO ] http-bio-9443-exec-2        70000007 100002 ###### com.vmware.vise.util.i18n.I18nFilter                              The preferred locale for session 100002 is set to: en_US

[2017-02-15T14:23:34.250Z] [INFO ] http-bio-9443-exec-2        70000007 100002 ###### com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl            Fetching SSO endpoints from CM

[2017-02-15T14:23:34.266Z] [INFO ] http-bio-9443-exec-2        70000007 100002 ###### com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl          Creating a CMServiceHolder for URI https://myserver.mydomain.local/cm/sdk?hostid=5d6bdf00-db61-11e6-9a06-000c299e8cce

[2017-02-15T14:23:36.295Z] [INFO ] http-bio-9443-exec-2        70000007 100002 ###### com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl          Retry won’t be attempted for CM https://myserver.mydomain.local/cm/sdk?hostid=5d6bdf00-db61-11e6-9a06-000c299e8cce for error: com.vmware.vim.vmomi.client.exception.ConnectionException — org.apache.http.conn.HttpHostConnectException: Connect to myserver.mydomain.local:443 [myserver.mydomain.local/192.168.x.x, myserver.mydomain.local/fe80:0:0:0:4858:3366:c0:39df%8] failed: Connection refused: connect

[2017-02-15T14:23:36.300Z] [ERROR] http-bio-9443-exec-2        70000007 100002 ###### com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl          Error when creating component manager service: https://myserver.mydomain.local/cm/sdk?hostid=5d6bdf00-db61-11e6-9a06-000c299e8cce com.vmware.vim.vmomi.client.exception.ConnectionException: org.apache.http.conn.HttpHostConnectException: Connect to myserver.mydomain.local:443 [myserver.mydomain.local/192.168.x.x, myserver.mydomain.local/fe80:0:0:0:4858:3366:c0:39df%8] failed: Connection refused: connect

Any help would be greatly appreciated!

500 sso error cannot connect to the vmware component manager

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Few days a ago, i tried to configure Single-Sign-On on VCSA 6.5.

Today I couldn’t login to vSphere web client VCSA:9443 and getting the error » [500] SSO error: Cannot connect to the VMware Component Manager » after rebooted VCSA.

Attached the error message of the vsphere_client_virgo.log

[2018-06-11T15:53:30.924+08:00] [WARN ] usage-data-collector-thread com.vmware.vsphere.client.telemetry.cmc.CollectorLoop Unexpected runtime error escaping the collector loop. The current loop execution will not complete successfully. The loop is not terminated and the next collection attempt will be executed on schedule. For more details on the current error, see the underlying exception: java.lang.RuntimeException: There was an error while getting SSO Server information and we cannot access the SSO Server. As a result no token can be acquired for solution user: vsphere-webclient For more information see the SsoService logs and the underlying exception: Cannot connect to the VMware Component Manager https:// VCSA.my.domian /cm/sdk?hostid=1091b2d1-10e9-4ee9-bcfa-3099bdd13f27 java.lang.RuntimeException: There was an error while getting SSO Server information and we cannot access the SSO Server. As a result no token can be acquired for solution user: vsphere-webclient For more information see the SsoService logs and the underlying exception: Cannot connect to the VMware Component Manager https://VCSA.my.domian/cm/sdk?hostid=1091b2d1-10e9-4ee9-bcfa-3099bdd13f27

Is there a way to revert back or revoke the SSO?

Источник

ThinkVirtual

VMware, NSX & Anything Cloud

Error : [500] SSO error: Cannot connect to the VMware Component Manager

I came along an interesting issue at work and was able to reproduce it in the lab . Sharing the way to fix it , while we check further for the cause of it.

Below were the steps performed to reproduce the problem

1. Build psca.xxxx.com by ISO. Site name “Default-First-Site”, Domain name “vsphere.local”.
2. Build pscb.xxxx.com by ISO and join psca.xxxx.com
3. Build vCenter instance “vcsa6.xxxx.com” by ISO and connect to psca.xxxx.com
4. Repoint vCenter instance to “pscb.xxxx.com” by KB 2113917.
5. Test Web Client and vSphere Client.
6. Reboot the 3 VMs and test again.
7. Disconnect network of vCenter instance VM.
8. Change DNS name of vCenter instance to different IP address on DNS server. >> Done successfully
9. Change IP address of vCenter instance to new IP by DCUI or command line. (I tested this with vami change through ssh as well as console UI on vcenter 6)
10. Connect network of vCenter instance VM.
11. Restart vCenter services and test again. (Web client fault here)

A server error occurred.
[500] SSO error: Cannot connect to the VMware Component Manager https://vcsa6.xxxx.bng/cm/sdk?hostid=fbf7282a-f940-4f6d-8180-58b1476c3e72
Check the vSphere Web Client server logs for details.

Error seen on vsphere-client-virgo.log for web-client under /var/log/vmware/vsphere-client .

[2016-01-18T11:46:43.240Z] [INFO ] http-bio-9090-exec-9 com.vmware.vise.util.session.SessionUtil Generated hashed session id: 100001
[2016-01-18T11:46:43.243Z] [INFO ] http-bio-9090-exec-9 70000001 100001 ###### com.vmware.vise.util.i18n.I18nFilter The preferred locale for session 100001 is set to: en_US
[2016-01-18T11:46:44.909Z] [INFO ] http-bio-9090-exec-9 70000001 100001 ###### com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl Retry wont be attempted for error: java.net.NoRouteToHostException: No route to host
[2016-01-18T11:46:44.917Z] [ERROR] http-bio-9090-exec-9 70000001 100001 ###### com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl Error when creating component manager service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:251)
at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:54)
at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:186)
at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:115)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:581)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:562)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:348)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:308)
at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:182)
at com.sun.proxy.$Proxy474.retrieveServiceInstanceContent(Unknown Source)

It clearly mentions as “”no route to host “.

At this point I tested forward /reverse lookup which was working fine , pings to both psca and pscb were working fine .

So , I repointed the vcsa back to psca and to my surprise the web-client started working fine.

Got the repoint done again back to pscb , and it failed again with the same error .

Post multiple log checks found that the /etc/hosts file on the vcsa still was having the old ip address although the new ip change was completed at step9.
Configured the hosts file with the correct ip address and restarted all services using command “service-control –stop -all ” and “service-control –start -all ”

Источник

500 sso error cannot connect to the vmware component manager

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Hopefully someone might be able to point me in the right direction here, I’m a bit out of my depth.

I have a LAB setup of 3x ESXi hosts, on one of which vcenter is installed.

All the ESXi hosts were added and everything was working very well. I needed to change the IP addressing of the network the three ESXi/vcenter hosts were on. Initially there was no problem, moved form 192.168.1.x/24 to 192.168.100.x/24. Again, initially everything seemed ok.

I think the problem I am now getting, which is when trying to access vsphere web client I get ‘[500] SSO error: Cannot connect to the VMware Component Manager’, started after the VM hosting vcenter rebooted, though I can’t be certain of this.

I’ve seen posts suggesting a requirement for entries in the hosts file of the vcenter server if forward/reverse DNS isnt working, but it is. I came across another post suggesting to reset the certificates using the certificate-manager.bat command, which I’ve tried but with no luck error stays the same after services/server reboot.

I pulled the vsphere-client-virgo.log but the only thing I could see in it was an entry of: failed: Connection refused: connect

In case it helps I’ve pasted the section below;

[2017-02-15T14:16:25.874Z] [INFO ] Timer-0 com.vmware.vise.util.debug.SystemUsageMonitor Summary: heap = 269.95 MB, threads = 87

Heap : init = 134217728(131072K) used = 283060008(276425K) committed = 376438784(367616K) max = 557842432(544768K)

non-Heap : init = 2555904(2496K) used = 189541640(185099K) committed = 210223104(205296K) max = -1(-1K)

No of loaded classes: 22227

Live Thread Count(w/o the live daemon threads): 6

Peak Thread Count: 90

Daemon Thread Count: 81

Tomcat Request-Processing Threads Count: 20

Blocked threads: 0

Waiting threads: 80

Threads blocked in Data Service: 0

Threads waiting in Data Service: 0

Threads blocked in Logback: 0

Threads waiting in Logback: 0

[2017-02-15T14:21:25.911Z] [INFO ] Timer-0 com.vmware.vise.util.debug.SystemUsageMonitor Summary: heap = 289.84 MB, threads = 87

Heap : init = 134217728(131072K) used = 303914664(296791K) committed = 376438784(367616K) max = 557842432(544768K)

non-Heap : init = 2555904(2496K) used = 189541640(185099K) committed = 210223104(205296K) max = -1(-1K)

No of loaded classes: 22227

Live Thread Count(w/o the live daemon threads): 6

Peak Thread Count: 90

Daemon Thread Count: 81

Tomcat Request-Processing Threads Count: 20

Источник

500 sso error cannot connect to the vmware component manager

After reboot of my vCenter 6.5 Windows embedded server, all service come back online as per normal (CPU Spikes for approx. 5 mins), then comes back down. When I try to launch the WEB GUI https://x.x.x.x/vsphere-client I get the following error:

Error : [500] SSO error: Cannot connect to the VMware Component Manager

vsphere_client_virgo logs show

[2018-03-19T16:03:33.434-04:00] [INFO ] cm-catalog-manager-pool-5 com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl Retry won’t be attempted for CM https://SITE.ca/cm/sdk?hostid=5a2db760-23ad-11e8-9352-005056ab1afc for error: com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException — Unexpected status code: 503

[2018-03-19T16:03:33.436-04:00] [ERROR] cm-catalog-manager-pool-5 com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl Error when creating component manager service: https://SITE.ca/cm/sdk?hostid=5a2db760-23ad-11e8-9352-005056ab1afc com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 503

Yet when I manually restart the VMWare vCenter Configuration Service in Services.msc and wait 5-10 mins it works fine.

I have waited 30+ minutes (maybe the services were taking a long time to start initially on boot).

Have a ticket open with GSS, they just took the vsphere logs and suggested I put that service on a delayed start. tried that, haven’t heard back.

Источник

500 sso error cannot connect to the vmware component manager

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Good day, and I hope yours is better than mine.

Just downloaded and set up VCSA 6.0 U2. Finally got it to join my domain*. Added admin group from domain and gave them permissions. Every time I tried to use NT authentication (the checkbox) it would error out.

I found and followed articles 2020970 and 21112283. Now I am unable to log into the web client nor the vSphere client.

web client yeilds this

A server error occurred.

Check the vSphere Web Client server logs for details.

vsphere client says

Windows session credentials cannot be used to log into this server (which is what started the 2 KBs above)

Cannot complete login due to incorrect user name or password (I tried SSO Admin, domain user, appliance root user)

I have tried the certificate replacement steps (option 8, then 8, then 3, then 4, then 8 again). Each ends with errors similar to this:

2016-03-29T18:35:36.382Z Updating certificate for «com.vmware.vim.eam» extension

Status : 0% Completed [Operation failed, performing automatic rollback]

Error while performing Cert Replacement operation, please see /var/log/vmware/vmcad/certificate-manager.log for more information.

Performing rollback of Root Cert.

followed by this at the end of the roll back

Updated 0 service(s)

Rollback Status : 40% Completed [Rollback machine Cert. ]

Rollback Status : 50% Completed [Rollback vsphere-webclient Cert. ]

Rollback Status : 60% Completed [Rollback vpxd Cert. ]

Rollback Status : 70% Completed [Rollback vpxd-extension Cert. ]

2016-03-29T18:36:23.960Z Updating certificate for «com.vmware.vim.eam» extension

Error while reverting certificate for store : vpxd-extension

Rollback Status : 0% Completed [Rollback operation failed]

Error while performing rollback operation, please try Reset operation.

please see /var/log/vmware/vmcad/certificate-manager.log for more information.

Thanks for the help from Stumped in Miami.

* And for those of you getting Error 11 on trying to join the domain go into the SCVA web portal, drill down to the actual network settings and switch the DNS to manual. Sorry I can’t be specific on the actual path to this setting. Although I gave it specific DNS at set up and a static IP I finally found that it had reverted to getting DNS from DHCP. Hope this helps.

Источник

Previously, I wrote a post about re-pointing the PSC and after a while I logged in to the same environment and I ended up with this error message on my screen. I was so frustrated as I have done few changes to this environment and thought something went wrong while I was doing these changes. See below error message that I received from my vCenter Server appliance.

So , I started to troubleshoot this issue. Simply it says check the vSphere Web Client logs for more details, that is the simplest way which we can start this. so I opened a ssh session to my vCenter server appliance and enabled the shell. I used below command to check the vSphere client log

cat /var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log

While I’m reading the logs I could find the timer errors and below errors in the logs

I configured my VCSA and PSC appliances to sync the time with ESXi hosts which were holding them. I was so sure about the time of the ESXi hosts. I checked the time of the appliances after checking the error logs and found that there is a huge time difference between these two appliances.

VCSA Appliance time:

PSC Appliance time:

So I disabled and enabled the synchronization to the ESXi hosts again (in my test lab no internet connectivity or no external NTP Server configured) and confirmed that the times are correct.

I’d suggest you to deploy a NTP Server (Linux based) and make sure your appliances sync with the NTP Server time in a Production environment. Time of these appliances should be exactly the same.

Stopped all the services using below command :

service-control --stop --all

Started the Services again :

service-control --start --all

Normally it takes sometime. After all I was able to connect to the vCenter server without any issues.

Another instance: VMCA Certificate regeneration – Error occured looking for solution user :: More than one solution user found

This issue appeared as the second instance of the same [500] error in one of my vCenter server and this time it was not related to the time synchronization of the vCenter Server but with the VMCA.

This vCenter was a Windows based vCenter server and same as the above scenario I checked the vsphere_client_virgo log file located in “C:ProgramDataVMwarevCenterServerlogsvsphere-clientlogs“.

This error was in the log

The solution user certificates were having some issues and only option was to re-generate the certificates.

To re-generate the certificates ran the certificate-manager tool located in “<installation_directory>/Program Files/VMware/vCenterServer/vmcad“, make sure to run it as an Administrator.

Select Option : 4 or 8 (both are doing the same ) and hit Y to start

Provide the SSO credentials to start the Certificate Operation and reconfigure the root.cfg file, also provide the input as shown in the below screen capture, leave blank and hit enter to keep the default values

Follow the same procedure to reconfigure the MACHINE_SSL_CERT.cfg, machine.cfg, vsphere-webclient.cfg, vpxd.cfg, vpxd-extension.cfg and at the end hit Y to generate the root certificate and all other certificates using VMCA.

Follow the same procedure to reconfigure the above .cfg files and hit Y at the end to start the regeneration process

It will start the Regeneration process and you will be able to login from the webclient once it completed the ssl regeneration process.

All the lookup services will be updated, this will take sometime and let it to complete

Once it completed the ssl regeneration loaded the vSphere webclient

These are based on my experience and I hope my post will help you to overcome with the similar issues.

If you found this post as useful please rate the post and share it!