Failed to launch the MKS client: The system cannot find the file specified

Evening troubleshooting…
I was sitting on #vmware irc channel today and i was interested in problem that one person had. He had fresh installation of esxi 5.1 on a brand new box, few vms, but for some reason he could not connect to vm remote console using vsphere client. We went through a lot of checking, many KBs and so on and on, cables, cards, nics, fw, dns… still nothing.
What we did at the end is that we were watching with ‘ tail -f /var/log/hostd.log ‘ the log, while he tried to open the console. And we finally saw :

2013-08-06T20:55:00.177Z [47696B90 verbose ‘Default’] Timed out reading between HTTP requests. : Read timeout after approximately 50000ms. Closing stream TCP(local=, peer=
2013-08-06T20:55:00.177Z [470E2B90 error ‘Solo.HttpSvc.HTTPService’] Failed to read request; stream: TCP(), error: N7Vmacore16TimeoutExceptionE(Operation timed out)
2013-08-06T20:55:02.061Z [47738B90 verbose ‘SoapAdapter’] Responded to service state request

So there had to be something with the connection/port.

vSphere client log was showing:

2013-08-06T15:07:51.557-05:00| vmrc| I120: VMClient_ConnectMksClientEx – connecting the MKS client
2013-08-06T15:07:51.557-05:00| vmrc| I120: VMClientConnectMKSClientEx
2013-08-06T15:07:51.558-05:00| vmrc| I120: cui::MKS::OnSetAttachedError
2013-08-06T15:07:51.558-05:00| vmrc| I120: cui::vmrc::DlgMgrImpl: “Unable to connect to the MKS: Failed to launch the MKS client: The system cannot find the file specified

vmware.log from vm had a lot of those entires:

2013-08-06T02:47:41.373Z| mks| I120: SSL Error: error:140780E5:SSL routines:SSL23_READ:ssl handshake failure
2013-08-06T02:47:41.373Z| mks| I120: SOCKET 6 (140) recv error 0: Success
2013-08-06T02:47:41.373Z| mks| W110: SOCKET 6 (140) Error during authd-VNC negotiation: (1) Asyncsocket error.

Firewall in windows was said to be disabled.

Solution: i asked if it possible to try to connect with vSphere client from another workstation which is not in Active Directory, as that computer from which that person was connecting to that esxi host was in active directory.
B.I.N.G.O 😉

That system was in AD where there were very strict policies, which were causing problems with making connections on 903 tcp port which is utilized when accessing the vm remote console. As soon as he made the connection from workstation that was not part of that AD/policy, VM console was opened without any issues.

23:33 -Krazypoloc- Holy shit the non domain machine works fine!
23:34 -Krazypoloc- Thanks for all your help man
23:35 -Krazypoloc- nostrovia
23:35 -Krazypoloc- 🙂
23:35 -gregu– no problem

🙂 I’m pretty sure that he was trying to say:
Na zdrowie !
here it is 😉

VAAI NFS Netapp plugin for vSphere unable to install using VSC

normally we should be able to install plugin from netapp for NFS VAAI support using the VSC console. I managed to do it for some hosts, then i started to update my hosts to latest build and from this moment i could no longer install the nfs vaai plugin for hosts using vsc. All hosts were updated to VMware ESXi 5.0.0 build-914586. Update manager could not help, vsc could not help… What helped :
1) download from netapp website the zip bundle
2) put it directly to host for example
3) using esxcli install it, so ssh to your esxi host

cd /vmfs/volumes/your_datastore_where_the_zip_is
/vmfs/volumes/2d1303c2-270be8c4 # esxcli software vib install -d file://$PWD/
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: NetApp_bootbank_NetAppNasPlugin_1.0-018
VIBs Removed:
VIBs Skipped:
4) Reboot host
5) Let’s party !!! vaai is now [ON] 🙂

You can then check if everything is correct
1) esxcli software vib list -> check for netapp part
2) vmkfstools -Ph /vmfs/volumes/your_datastore -> check for : “NAS VAAI Supported: YES”
3) check in vSphere client -> configuration/storage if this datastore has now Supported value in Hardware acceleration
4) After installation you should see file in here on your esxi host:
After host reboot you should see file in here on your esxi host:

When troubleshooting plugin installation using netapp vsc, you can check log : /var/log/esxupdate.log to see why in your case it is not installing it correctly

Issues with vmmonitoring in HA clusters while using vsphere client 5.0.0 build 455964, vm monitoring with vmware tools down will not restart failed vm

I wanted to share with everybody this ‘news’.

While trying to create vm monitoring within HA cluster using vm monitoring only i went into some issues. VM monitoring was not working. I thought there is not that much to configure to have this working right ? Open cluster settings, go to vm monitoring section

Continue reading

Change vnic type from / to e1000, Flexible, Vmxnet, EnhancedVmxnet, and Vmxnet3, and Unknown with Set-NetworkAdapter. UPDATED!

What if you noticed that your vms are running on wrong network card type ? Let’s say you want e1000 instead of vmxnet3 for some reason.There is a great cmdlet set-networkadapter. This will help us out in that kind of situation(Thx Rafael!).
Right, so what set-networkadapter can do for us ? (by this time you should read the get-help set-networkadapter -full). So now, like you already know 😉 it can do a lot for us! But what i want from it right now, is to help me with changing the adapter type. I want to change it from vmxnet 3 to e1000, would be cool if i will not need to shutdown vm too 😉 Unfortunately it will not be so cool at all !!! VM has to be powered off to make this change properly. Please do not do this while vm is up and running.
Continue reading

Locate vms that are in particular cluster and are using particular datastore in powercli

A quick one :
Trying to find which vms are residing on datastore :”datastore_name” and are located in cluster “your_cluster”

Get-Cluster "your_cluster"|Get-vm |?{($_.extensiondata.config.datastoreurl|%{$}) -contains "datastore_name"}
Get-Cluster "your_cluster"|Get-vm |?{($_.extensiondata.config.datastoreurl|?{$ -eq "datastore_name"})}

It’s easier if the vms reside on particular datastore and you do not care in which cluster they are:

(Get-Datastore -Name 'datastore_name').Extensiondata.Vm|%{(Get-View -Id $_.toString()).name}

And approach where you want to check all datastores in specific cluster:
So i was thinking about this and came out with that 😉 :

get-vmhost -Location "Cluster_01"|get-datastore|%{$ds=$_; $ds.Extensiondata.Vm|%{$_|select @{n='vm name';e={(Get-View -property name -Id $_.toString()).name}},@{n='ds name';e={$}}  }}

In case you want to check serveral datastores with known names for vms you can do this, assuming that for example names are written in file : c:\dsfile.txt

Get-Datastore -Name (get-content c:\dsfile.txt) | %{$temp=$_; $temp.extensiondata.vm | % { $_ | select @{n='VMName';e={(get-view -property name -id $_).Name}},@{n='ds';e={$}}}}