PowerCLI Guest OS Cmdlets Error - The 'propSet' paramter should not be null.

[genericUserNam4]

Hey,

I am using the PowerCLI cmdlets for VM management, they all seem to work fine except for the cmdlets regarding interaction with the guest OS on my VMs.

Calling the Invoke-VMScript successfully executes a Script on a VM, but returns the following Error Message in Powershell:

Calling Copy-VMGuestFile returns the same Error, however i can not transfer files from the VM to my system. The full Error is:

FullyQualifiedErrorId : Client20_VmGuestServiceImpl_DownloadFileFromGuest_DownloadError,VMware.VimAutomation.ViCore.Cmdlets.Commands.InvokeVmScript

The Server hosting the VMs is in a different network than my system executing the PowerCLI cmdlets, and it seems to me that outgoing requests from the VMs Guest OS to my system are blocked, while i can send and execute requests to/on the VMs. I can not connect to the server from the Guest OS in a VM.

What causes the Error "The 'propSet' paramter should not be null." ?

Do i have to open any ports regarding the VMs?

Thank you for your help.

[LucD]

Using remote sessions is indeed an alternative, but opens another can of worms imho.
I'm not really a fan of allowing winrm all over the place.

If you ever find the actual reason for this, I would be very interested to learn about the actual cause of the problem.

[genericUserNam4]

it might just be some obvious rookie mistake, since i just started using PowerCLI, but i can't figure it out at the moment.

i will post an answer if we find the cause of the error.