VIX_E_HOST_TCP_SOCKET_ERROR in FoundryVMOpenSocketToVMXThroughAuthd()

[jociz]

Hello,

VIX API VixVM_PowerOn does not work on VMware Workstation 10 after upgrading from version 9 and no virtual machines could be started with VMware VIX API.

There is no vmware log file created. But I found a vmware-vix-14996.log in the temp folder.

Here is a portion of this vix log file:

2014-07-19T19:55:00.230+02:00| vthread-3| I120: CnxAuthdConnect: Returning false because CnxAuthdConnectPipe failed

2014-07-19T19:55:00.230+02:00| vthread-3| I120: CnxConnectAuthd: Returning false because CnxAuthdConnect failed

2014-07-19T19:55:00.230+02:00| vthread-3| I120: Cnx_Connect: Returning false because CnxConnectAuthd failed

2014-07-19T19:55:00.230+02:00| vthread-3| I120: Cnx_Connect: Error message: Failed to read vmware-authd port number: Cannot connect to xxxxxx.vmx

2014-07-19T19:55:00.230+02:00| vthread-3| I120: Vix: [16920 foundryVMPowerOps.c:6004]: Error VIX_E_HOST_TCP_SOCKET_ERROR in FoundryVMOpenSocketToVMXThroughAuthd(): unable to contact authd: Failed to read vmware-authd port number: Cannot connect to VMX: xxxxxx.vmx

Do you have any idea or clue on what may be the root of the problem?

[rachelsg]

Hi

Welcome to communities.

Its due to permission issues ,

Here you will find all error code

https://www.vmware.com/support/developer/vix-api/vix16_reference/errors/errors.html

[guptapratham366]

Thank you, but found the solution.

I got it fixed by setting the value to "headless" attribute in builder of Packer build JSON file to "true". This was previously set to "false" and used to work in 17.0.2 version of VMware workstation. Somehow, it is not working in version 17.5.1 of VMware workstation if "headless" attribute is set to "false" for Windows builds.

[guptapratham366]

Also to clarify: VIX_E_HOST_TCP_SOCKET_ERROR was not the issue.

My Packer vmware-iso builds were getting stuck at the line and not proceeding further in the packer log:

==> vmware-iso: Starting virtual machine...

Though, in the background the VM was getting started, booting and running all the scripts and the updates. However, it was not able to communicate with VMware workstation that the VM has started.