Can you check if the vmware.log (found in the VM's folder) contains anymore clues?
You can also try to restart the VMware Tools inside the guest OS.
Any FW rules active inside the guest OS that might block?Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
Thanks LucD for your reply.
Unfortunately the vmware.log doesn't contain any relevant logs, from what I can see in there everything is working correctly.
In fact the script has been processed correctly inside the guest OS but the Invoke-VMScript is not able to retrieve the result.
The firewall in the guest OS shouldn't matter because the Invoke-VMScript doesn't use the guest OS network to do the job that by the way is about configuring the network itself.
Also if I run the invoke-vmscript against the physical host instead of the vcenter server, it works so the problem shouldn't be related to the guest OS at all.
The guest OS anyway has been restarted many times and re-deployed too and the problem is affecting all the VMs
Did you disable the DepreciationWarnings?Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
Did that too, same result.
In fact, as you can see from my original post is not a deprecated warning message but an actual error.
Yes, I saw the error from the Invoke-VMScript cmdlet, but I meant any depreciation messages from cmdlets inside the script you are running in the guest OS.
That's why you should place this as the 1st line in the script you run in the VM.
Can you check if there is anything in the log files in /var/log/vmware-vmsvc.log?
And is there a file in the directory in /tmp/vmware-<your username>*?Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
Sorry, I didn't understand about the deprecation warning..
Anyway the script I am running using the Invoke-VMScript cmdlet is a simple "netsh interface ip set address `"Ethernet0`" static $($IP) $($NETMASK) $($GW)"
but can be a "ping" or a "dir". All command run correctly but same error when the Invoke-VMScript cmdlet try to get the result.
To notice that I have the same problem with Copy-VMGuestFile in both directions. If I try to copy a file from the guest VM to the local machine I can see the vmware-tools accessing and reading the file in the guest VM, the Copy-VmGuestFile create a empty file in my local machine and then I get the error.
and again if I run the command against the vmware physical host is working while if I run against the vcenter it doesn't. Vcenter, physical host and my machine are all in the same network.
Forgot to say:
the vmware-vmsvc.log (vcenter) doesn't report anything and there is no /tmp/vmware-<username> directory
Just to clarify, the Invoke-VMScript works when connected to the ESXi node, but not when connected to the vCenter?Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
I got a vcenter with three ESXi node and vmware vpshere 6 standard license.
Everything installed from scratch with the following versions:
vcenter version: 6.7.0, 11727113
esxi host version: 6.7.0, 10764712
Is the PSC embedded or standalone?Blog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
You are not the only one experiencing this it seems.
See Error running Invoke-Vmscript - An error occurred while sending the request. FullyQualifiedErrorId : Client20_VmGuestServiceImpl_DownloadFileFromGuest_DownloadError,VMware.VimAutomation.ViCore.Cmdlets.Commands.InvokeVmScriptBlog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
The PSC is embedded
Interesting I looked everywhere and I didn't find anybody expect a guy but the thread didn't go nowhere
I ran into the same issue. I have two ESXI clusters managed by one vCenter. I connected to vcenter using powercil.
One interesting thing is, I was able to invoke the script on one of the VM hosted on one cluster but not the other. No help from VMware logs.