Are you connected to more than one vCenter?
This looks strange. Can you please let us know:
1. Are you using FQDN?
2. Provide an example how you're connecting to your VC (connect-viserver ...)
3. Describe the deployment you have (mxn)?
4. Can you capture a Fiddler log, so we can see at which point the connection is failing? Depending on what we see here, we may also need a wireshark log (if this is a TLS-related issue)
I am also experiencing issues with New-TagCategory on PowerCLI 6.5.1
PS C:\Scripts> New-TagCategory -Name Department
New-TagCategory : 8.5.2017 14.02.20 New-TagCategory vSphere single sign-on failed for connection '/VIServer=vclass\adm
inistrator@vcva01:443/'. Future operations which require single sign-on on this connection will fail. The underlying cause was: Cannot parse request lifetime [2017-05-08T11.00.11.781Z; 2017-05-08T11.05.11.781Z) :: Unparseable date: "2017-05-08T11.00.11.781Z"
At line:1 char:1
+ New-TagCategory -Name Department
+ CategoryInfo : NotSpecified: (:) [New-TagCategory], CisException
+ FullyQualifiedErrorId : ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.NewCategory.Error,VMware.VimAutomation.ViCore.Cmdlets.Commands.Tagging.NewTagCategory
This issue is caused by region settings on Windows system, if I change locale from Finnish to English (US) then this works fine.
2 people found this helpful
Yes i am connected using FQDN and only connected to one vCenter.
i had to completely uninstall powercli and then reinstall to get this working.
any news here?
We have the same issue. It happens with and without FQDN and only for the New-TagCategory, Get-TagCategory, Get-Tag and New-Tag command. Everything else works (as far as I know).
I connect using Connect-VIServer <servername>
If I connect using Connect-VIServer <servername> -Credential (Get-Credential) I don't have this issue.
PowerCLI Version is 6.5 Release 1 Build 4624819