Did you check in the Web Client if there is a service (Administration-System Configuration-Services) that has a warning or is in a critical state?
The fact that the message queue seems to have reached the maximum quota, could indicate that there is a service in trouble.
Just checked to make sure, but VCenter reports 20 good services and 7 not applicable.
Also already update VCSA to the latest version (22.214.171.12400 Build 6671409) this morning, just to make sure.
So both VCenter / local machine were rebooted.
There have been somewhat similar mentions of failing ssi.
Did you try the following:
- connect to the vCenter with a FQDN
- connect to only 1 vCenter
- uninstall/install PowerCLI
we always connect using FQDN (just tried not fully qualified to make sure, but the same thing happens)
we also only have 1 vcenter
Uninstalled powercli this morning (6.5.0) and installed the latest gallery version
Thanks for the assistance
We have come across this same issue. It appears to be related to the size of the user's token. A large number of group memberships can cause this. Using firstname.lastname@example.org for credentials is a work around.
We are also experiencing this issue, any status update from VMware?
Just wanted to note that this still appears to be an issue even with the latest version of PowerCLI (11.0.0 build 10380590) when using pass-through authentication to connect to a vCenter (not specifying credentials for Connect-VIServer). When using pass-through auth, the various Tag cmdlets fail with the "vSphere single sign-on failed for connection" error message that was posted above.
However, if I create a credential object and pass that to Connect-VIServer, the Tag cmdlets work. E.g.,
$cred = Get-Credential
Connect-VIServer vcenter -Credential $cred
This works if you're running things by hand, but is not a great workaround if you're trying to use the Tag cmdlets in an unattended script.