So I'm running into an odd issue I can't seem to find any info on at all. Of course maybe it's PEBCAC based >_>. There are several commands that have been hanging when executed against my hosts, including even the basic "Get-EsxCli". It's very easy to cause and reproduce, it's as simple as connecting to the host, running Get-EsxCli, and the end result is I have to force close the PowerCLI instance. Here's an example of a sequence of commands that will lock up my PowerCLI instance:
Connect-VIServer "hostname.company.com" -User xxx -Password xxx
Get-EsxCli
The Connect-VIServer cmdlet executes without issue, when I execute the Get-EsxCli cmdlet I've let it run for almost an hour with no results. I've executed the same commands from fresh PowerCLI sessions and PowerGUI sessions with the same result. Another cmdlet that has been causing the same issue is Add-VmHostNtpServer, as well as a few others. The majority of PowerCLI cmdlets work, even host based ones, and I can execute scripts that don't have a cmdlet which is causing this issue just fine. (For a while I thought I had infinite loops in some of my scripts or something until I broke them down to find this as the issue.)
Steps I've taken to attempt to resolve:
Reboot Host
Try different Host(s)
Run from fresh PowerCLI and PowerGUI instances
Reinstall PowerCLI 5.1 U2
Reboot Client machine
Any ideas?
~Brandit
*Edit - As far as specific version, the primary I'm using for testing is ESXi 5.0.0 U1.
*Update - I have confirmed that SOME hosts still work, I expanded which hosts I was checking. Hmm... guessing it's host specific in that case.