VMware Communities
laucha13
Contributor
Contributor

"Unable to connect to the MKS: Too many socket connect attemps, giving up."

Hello... I'm having the following message on VM Workstation 14 Pro (Win 7 Pro VM on Win 10 Pro Think Pad W541 i7 laptop) when I try to start it.

"Unable to connect to the MKS: Too many socket connect attemps, giving up."

I used to run 3 VMs at the same time from an external SSD with no problems, Thursday everything was well.

Friday I started having this issue, no new installation or windows updates done.

Once the VM is started, when I switch in "console view" I can see the VM is running, I can see the VM desktop but when I click inside to give focus, my screen becomes black.

From this state I press Tab key to see if the keystroke is detected but when I go back in "cosole view" there is no change, same desktop field has the focus, so keystrokes are not detected, it's not only a display issue.

Tried the following actions with no results:

- Deactivated firewall and antivirus

- Started all services described in this and other forums

- Full uninstall and reinstall the VM Workstation 14 Pro

- Execute the VM form internal HDD

- Running other "template" VMs that I now work well in other laptops

- The same VMs that are on my SSD and that doesn't works on this laptop, work well on another laptop.

As I said I've passed through most of popular fixes with no results.

On the log I can see a lot of error messages about File Directory but don't understand very well why they are originated. Following is an example (full log is attached).

For any reason VM Ware has changed file directories ?

2018-05-14T08:48:47.592-04:00| vmui| I125: VTHREAD initialize main thread 1 "vmui" host id 12672

2018-05-14T08:48:47.592-04:00| vmui| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)

2018-05-14T08:48:47.592-04:00| vmui| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware\VMware Workstation): Cannot create a file when that file already exists (183)

2018-05-14T08:48:47.592-04:00| vmui| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)

2018-05-14T08:48:47.592-04:00| vmui| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware\VMware Workstation): Cannot create a file when that file already exists (183)

2018-05-14T08:48:47.592-04:00| vmui| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)

2018-05-14T08:48:47.592-04:00| vmui| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware\VMware Workstation): Cannot create a file when that file already exists (183)

2018-05-14T08:48:47.592-04:00| vmui| I125: DictionaryLoad: Cannot open file "C:\Users\Charles\AppData\Roaming\VMware\config.ini": The system cannot find the file specified.

I add a .zip file with message print screens, logs, services status and about page.

Any comment will be greatly appreciated !!

Thanks for your help!

0 Kudos
2 Replies
Harwise
VMware Employee
VMware Employee

2018-05-14T08:49:24.023-04:00| vmui| I125: CnxAuthdConnect: Returning false because CnxAuthdProtoReadResponse2 failed

2018-05-14T08:49:24.023-04:00| vmui| I125: CnxConnectAuthd: Returning false because CnxAuthdConnect failed

2018-05-14T08:49:24.023-04:00| vmui| I125: Cnx_Connect: Returning false because CnxConnectAuthd failed

2018-05-14T08:49:24.023-04:00| vmui| I125: Cnx_Connect: Error message: Connection terminated by server

2018-05-14T08:49:24.023-04:00| vmui| W115: MKSCConnection: Failed to connect mkscontrol server (path=F:\Windows7x64Pro_AutocadElectrical2014old\Windows 7 x64_Empty.vmx, err=Connection terminated by server).

So something wrong when connecting to the authd. Considering you have checked the status of the authd service and closed all aniti-virus and firewall applications, I can hardly tell the reason.

Maybe you can run this VM as a shared VM and have a try, if it is an acceptable work around.

0 Kudos
laucha13
Contributor
Contributor

Exactly same problem, as the last time.

Extremely disappointed with VM people that still did not fix this problem.

Black screen, nothing to do, days lost trying to fix it !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I will continue to install, uninstall, changing configurations ... maybe the problem will fix by itself as the las time.

We will start trying other virtualization softwares ... can't trust VM Ware any more.

0 Kudos