forbzie
Contributor
Contributor

PowerCli 12.2.0 Start-VM Value cannot be null

Hi,

I updated PowerCLI to version12.2.0 and connected to vCenter 7 Update 1d.

When running Start-VM or Stop-VM i get the following:

start-vm -vm vm-name

Start-VM: Start-VM Value cannot be null. (Parameter 'key')

If i check vCenter i can see the CmdLet still works as the VM starts/stops ok.

This appears to be happening to Stop-VM and probably other cmdlets too, anyone experiencing this as well?

Thanks 

 

0 Kudos
9 Replies
LucD
Leadership
Leadership

I'm using VCSA 7u1 build 17491160, and I don't see those errors.
Which build are you using?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
forbzie
Contributor
Contributor

Hi,

 

This version tested ok - vCenter  6.7.0 16709110
 This version has the issue - vCenter 7.0.1 17327586

Using PSCore 7.1

 

Thanks 

0 Kudos
LucD
Leadership
Leadership

I tested in PSv5.1 and PSv7.1.2 (on Windows & Ubuntu), in neither do I see any errors.

I would suggest opening an SR.
GSS might claim you need an SDK Support contract for PowerCLI, but that is not correct.
Point them to PowerCLI Support Breakdown


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
LucD
Leadership
Leadership

When you open an SR, can you include the output of the Get-ErrorReport cmdlet.
See Improving PowerCLI Support with Get-ErrorReport for instructions on how to do that.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
vXav
Expert
Expert

I had a similar issue and if I remember correctly I fixed it by changing the Windows region language to match the Windows build.

0 Kudos
jforbes22
Contributor
Contributor

ok thanks LudD

Error report captured and case raised with VMware, lets what happens.

0 Kudos
LucD
Leadership
Leadership

Do you happen to have the SR number?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
jforbes22
Contributor
Contributor

yep, SR21199525702

0 Kudos
LucD
Leadership
Leadership

Thanks, I passed it along to the PowerCLI team


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference