We are currently developing an automation portal with:
CPSC,
CPO
UCS Director.
But, I'm faced to a really annoying problem:
The task Execute VM Command and VIX Script are unusable.
I did the troubleshoot with:
PowerCLI, Result => Command executed correctly
With the task inside a really simple workflow => Executed but without effect on the Virtual Machine
With VIX Script =>
Apr 20, 2016 16:22:36 UTC [VIXActionHandler] - account details VMName :WINDOWS_03 , Host : esxi.locql , OS Type :microsoft windows server 2012 (64-bit) , ExitCode :3006
Apr 20, 2016 16:22:36 UTC Task: VIX Script (Execute VIX Script) failed with error - Task failed with VIX Error Code: 3006 and status message: The virtual machine needs to be powered on, selectedContext=
Apr 20, 2016 16:22:36 UTC Task #1 (VIX Script (Execute VIX Script)) failed after 3 seconds
Apr 20, 2016 16:22:36 UTC Input/Output values for Task #1 (VIX Script (Execute VIX Script)):
Apr 20, 2016 16:22:36 UTC [Local Input: Select VM = 133]
Apr 20, 2016 16:22:36 UTC [Local Input: Credential Type = Login]
Apr 20, 2016 16:22:36 UTC [Local Input: Login = Administrator]
Apr 20, 2016 16:22:36 UTC [Local Input: Password = **masked-value**]
Apr 20, 2016 16:22:36 UTC [Local Input: Script = C:\Scripts\SetIPAddress.ps1 -macaddress 00-50-56-AC-58-AC -ipaddress *.*.*.* -netmask 255.255.255.0 -gateway *.*.*.*]
Apr 20, 2016 16:22:36 UTC [Local Input: Undo Script = null]
Apr 20, 2016 16:22:36 UTC [Local Input: Error Codes = null]
Apr 20, 2016 16:22:36 UTC [Local Input: Output Display = true]
Apr 20, 2016 16:22:36 UTC [Output: EXIT_STATUS_CODE = 3006]
Apr 20, 2016 16:22:36 UTC [Output: ERROR_STATUS_MESSAGE = The virtual machine needs to be powered on]
Apr 20, 2016 16:22:36 UTC Completed workflow item number 1, with status Failed
I tried with the command line directly on the UCSD:
DEBUG: Success jobHandle 34603071
DEBUG: Success hostHandle 34603070
DEBUG: Before Opening VM
DEBUG: Opening VM....
DEBUG: Opened the VM
DEBUG: waiting for tools
failed while waiting for tools in virtual machine 3006 ((null))
Has someone a workaround or a solution about executing command inside a VM with the VMware Agent ?
