This issue can occur if you logged into the VirtualCenter or the ESX host using VMware Infrastructure (VI) Client and do not have Console Interactions permissions.
To solve this issue :
Grant all users logged into the VirtualCenter or the ESX host using VI Client require Console Interaction permissions.
To grant Console Interaction permissions:
- Login to VirtualCenter or the host using VI Client.
- Select the host (if logged in to the host) or the datacenter (if logged in to the VirtualCenter)
- Click the Permission tab.
- Right-click in the blank space and choose Add Permissions.
- Under Users and Groups, click Add.
- Select the user experiencing the issue.
- Click Add.
- Click OK.
- Under Assigned Role, click on the plus sign next to All Privileges.
- Click on the plus sign next to Virtual Machine.
- Click on the plus sign next to Interaction.
- Select Console Interaction.
- Select Propagate to Child Objects.
Hope this will help ...
Best regards
Your Oscar
Hello.
In my case, were problems with DNS.
I used the IP to connect to my vCenter and all correct!!!
You can try with the Ip, not with hostname. It works for me.
A test I did, does it work if you launch a RDP against Vcenter and then from there use the Vshepere client? In my opinion, an issue with DNS. Perhaps,two IPs for one hostname.
In my real case, it worked fine when I picked up the good IP. 
