2016年1月21日 星期四

“Unable to open MKS: Internal Error” when opening virtual machine console (2116542)

“Unable to open MKS: Internal Error” when opening virtual machine console (2116542)

轉載至 http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2116542


Symptoms

After adding an ESXi host to vCenter Server 6.0 with running virtual machines, you experience these issues:
  • Opening a virtual machines console fails the vSphere Client and vSphere Web Client

    Note:  Not all virtual machines experience this issue.
  • Opening a virtual machine console in the vSphere Client displays one of these error:

    Unable to open MKS: Internal Error
  • Opening a virtual machine console in the vSphere Web Client displays one of these errors:
    • The console has been disconnected. Close this window and re-launch the console to reconnect.
    • Failed to initialize SSL session to remote host
  • In the /vmfs/volumes/virutal_machine_datastore/virtual_machine_folder/vmware.log file, you see entries similar to:

    <YYYY-MM-DD>T<TIME>| mks| W110: SSL: Unknown SSL Error
    <YYYY-MM-DD>T<TIME>| mks| I120: SSL Error: error:14094438:SSL routines:SSL3_READ_BYTES:tlsv1 alert internal error
    <YYYY-MM-DD>T<TIME>| mks| I120: SSL Error: error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure
    <YYYY-MM-DD>T<TIME>| mks| I120: SOCKET 15 (143) recv error 0: Success
    <YYYY-MM-DD>T<TIME>| mks| W110: SOCKET 15 (143) Error during authd-VNC negotiation: (1) Asyncsocket error.

Cause

This issue is caused by the SSL certificates are updated by the ESXi host when connecting to the new vCenter Server.  These certificates are used by the console and may not be updated with the virtual machine running.

Resolution


This is a known issue affecting ESXi 6.0.

To resolve this issue, use one of these options:
  • Power off and Power on the virtual machine.
  • Migrate the virtual machine to another ESXi host using vMotion.
  • Suspend and then Resume the virtual machine.

    Note: The virtual machine must be powered off for the changes to take affect.  A warm reboot will not resolve the issue.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.









沒有留言:

張貼留言