Just curious if anyone else is see this as well....
After connecting to a vcenter I try a
Get-Compliance -entity VM
Then my powershell/powercli session crashes...
I have tried this with Powershell x86 and 64 bit, and PowerCLI x86 and 64 bit....it crashes everything.
The only difference I have seen is in the x86 versions I actually get an error..
"This process was terminated due to StackOverfloxException"
Although I understand the error, I can't really resolve it either...
Is anyone else seeing this? I am just trying to figure out if it is just me or if there is some kind of bug with the cmdlet.
That's funny, I'm seeing the same thing in PowerGui ScriptEditor:
http://powergui.org/thread.jspa?threadID=18794
- ScriptEditor 3.2.0.2237
- Windows 2008 R2
- VMware vSphere PowerCLI 5.0.1 build 581491
- VMware.VumAutomation 4.1.0.5395 (I can't use v5.0 it's not compatible with vCenter < 5.0)
It's been stable when running in PowerCli x64 and for me I'm not seeing Powershell crash outside the editor.
Ben
PowerGUI script editor also crashes for me when I use VUM cmdlets. Did anyone ever get a resolution for this? The commands work when using the VMware PowerCLI command prompt.
Check the release notes to enusre the compatibility.
http://www.vmware.com/support/developer/ps-libs/vumps/vumps50/vumps50-20118-releasenotes.html
To use Update Manager PowerCLI 5.0, you need to have installed the following software:
Update Manager PowerCLI 5.0 works only with Update Manager 5.0.
VMware vSphere Update Manager PowerCLI 5.0 works on the 32-bit and 64-bit versions of the following operating systems:
http://www.vmware.com/support/developer/ps-libs/vumps/vumps41/vumps41-20107-releasenotes.html
To use vCenter Update Manager PowerCLI 4.1, you need to have installed the following software:
Update Manager PowerCLI 4.1 works only with Update Manager 4.1.
vCenter Update Manager PowerCLI 4.1 works on the 32-bit and 64-bit versions of the following operating systems:
I have the latest v5 version running for vCenter, VUM, vSphere CLI and VUM CLI. My local computer is running Win 7 x64. I have .NET v4 installed.
i'm also getting this error. has anyone found a resolution? i would like to get a list of updates as a report for the host.
I have the same problem with a Windows 7 (x64) and Windows 8 (x64) system. Both with Windows Management Framework 3.0 (Native in Win8, manually installed in Win7). Another System with Windows 7 and PowerShell v2 works without any problems.
I don't know if the problem is related to the Powershell Version, but for me setting the compatibility mode to Version 2 helped:
You can check the version with $host:
PowerCLI C:\> $host
Name : ConsoleHost
Version : 3.0
To change the version, start PowerShell with the -version 2 argument:
%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -version 2
Message was edited by: FL0G [Compatibility mode added]
Definitely appears to be a Powershell Version 3 issue. If you start powershell.exe with the -Version 2 parameters the VUM cmdlets work.
