I get stackoverflow error when I run "get-baseline -entity "clustername"", any ideas? This is running on Windows 2008 R2 server.
I have PowerCLI 5.8 installed with VUM 5.5 U2 PowerCLI.:
Get-PSSnapin | ft
Name PSVersion Description
---- --------- -----------
Microsoft.PowerShell.Diagno... 3.0 This Windows PowerShell sna...
Microsoft.PowerShell.Core 3.0 This Windows PowerShell sna...
Microsoft.PowerShell.Utility 3.0 This Windows PowerShell Sna...
Microsoft.PowerShell.Host 3.0 This Windows PowerShell sna...
Microsoft.PowerShell.Manage... 3.0 This Windows PowerShell Sna...
Microsoft.PowerShell.Security 3.0 This Windows PowerShell Sna...
Microsoft.WSMan.Management 3.0 This Windows PowerShell sna...
VMware.VimAutomation.Core 2.0 This Windows PowerShell sna...
VMware.VimAutomation.Vds 2.0 This Windows PowerShell sna...
VMware.VumAutomation 2.0 This Windows PowerShell sna...
VMware.VimAutomation.License 2.0 This Windows Powershell sna...
VMware.DeployAutomation 2.0 Cmdlets for Rule-Based-Depl...
VMware.ImageBuilder 2.0 This Windows PowerShell sna...
VMware.VimAutomation.Storage 2.0 This Windows PowerShell sna...
This is the version table
$psversiontable
Name Value
---- -----
WSManStackVersion 3.0
PSCompatibleVersions {1.0, 2.0, 3.0}
SerializationVersion 1.1.0.1
BuildVersion 6.2.9200.16398
PSVersion 3.0
CLRVersion 4.0.30319.1026
PSRemotingProtocolVersion 2.2
Can you try with PowerCLI 6.0 R2 ?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Okay, following some advice from google search, I need to launch powershell in version 2 compatible mode. After doing that. I was able to run get-baseline without error... what gives?
That is indeed a known error, but should be fixed in the latest release.
Hence my question if you can upgrade.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Thanks for the reply, but it looks like this issue has been going on since version 5.1!! I guess 6.0 is an overhaul, hopes they don't carry this problem over.