All of a sudden I get errors in my existing scripts which use Get-Tag or Get-TagAssignment.
This is the error:
get-tag : 19/10/2017 15:15:20 Get-Tag vSphere single sign-on failed for connection '/VIServer=domain\firstname.lastname@example.org:443/'. Future operations which require single sign-on on this connection will fail. The underlying cause was: The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.
At line:1 char:1
+ get-tag -Name *SQL*
+ CategoryInfo : NotSpecified: (:) [Get-Tag], CisException
+ FullyQualifiedErrorId : VMware.VimAutomation.ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.GetTag.Error,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.GetTag
Whenever I search for the error, I only see resolutions for WCF applications/services...
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.
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
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.
Have a .csv file with the VM names in first column and VM tags I want to assign them in the subsequent columns (Tags already created on the VCSA)
Can the rCisTag be used to complete the above as the Tag commands (Get-Tag etc..) seems to be still not working even with latest powercli (using VCSA 6.5U2)
If you can provide please provide an example
That's a bummer.
The rCisTag module provides the same set of cmdlets as the regular Tag related cmdlets in PowerCLI.
Just the name has been slightly changed, for example, the Get-Tag cmdlet becomes the Get-rCisTag cmdlet.
Have you also looked at another community module named VMware.Community.CISTag , it tends to be faster than the rCisTag module cmdlets.
Can you eventually show a mockup of that CSV layout?
What exactly is in there (VMname,TagCategory,TagName...)?
Is there more than 1 tag in a row?
This has been fixed in PowerCLI 12.3. At least when the issue was caused by a large Kerberos ticket using pass through authentication, because the size was limited to 12288 byte. Now the limit is 65535.