VMware Cloud Community
CNenad
Contributor
Contributor

Problems with VMRC 10 from PowerCLI and WebConsole after re-install

Hi Smiley Happy

I've had functional environment:

Win 10 1607

VMware-PowerCLI-6.5.0-4624819

VMRC 8.x

Client Integration Plug-in 6.0

I could open VM console from PowerCLI or from Web Console (ESX Virtual Center 6.0) or using web plug-in.

After updating to Win 10 1703 PowerCLI stopped to work. Ok, I saw, there is new version, 6.5.1 so I've uninstalled previous version and install new modules. After trying to open VM console and getting error first I've uninstalled VMRC 8.x and installed VMRC 10.

Now when I run open-vmconsolewindow vm_name from PowerCLI I've get following error:

VMWare Remote Console unrecoverable error (vmrc)

Exception 0xc06d007e

When I try to open VMRC from Web Console clicking on link Launch Remote Console VMRC window is opened and after some time I've get error:

Unable to connect the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period

The only way I can connect to VM console now is using web plug-in from Web Console: Find VM, choose Actions, choose Open Console.

What is going on with PowerCLI and VMRC and Web Console and VMRC ? How can I get back functional environment ?

Thank you

Kind regards

Tags (2)
Reply
0 Kudos
10 Replies
CQuartetti
Hot Shot
Hot Shot

Can your instance of VMRC access server port 902? Did VMRC 8.x have a firewall exception where VMRC 10 does not?

Please look at a recent log file %TEMP%\vmware-%USERNAME%\vmware-vmrc-*.log and let me know if you see a sequence similar to the one posted in this thread: vSphere Client - Console Error where

CnxOpenTCPSocket: Cannot connect to server xx.xx.xx.xx:902: ...

is followed by

VMClient_ConnectMksClientEx - Remote socket connection failed.

VMClient_ConnectMksClientEx - trying local socket connection to /vmfs/volumes/xxx/xxx.vmx

Reply
0 Kudos
CNenad
Contributor
Contributor

Hi

Thank you for your reply.

Here are similiar errors from log (I have ommited date time and vmrc column)

I125: vmdbLayout::Cnx::ConnectMksClient: Connecting via remote MKS

I125: VMClient_ConnectMksClientEx

I125: VMClient_ConnectMksClientEx - trying remote socket connection to esx_servername.domain.tld:902 /vmfs/volumes/guid/vmnamefolder/vmname.vmx

I125: VMClientConnectSocketEx

W115: SSL: Unknown SSL Error

I125: SSL Error: error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol

W115: SSL: connect failed (1)

I125: CnxAuthdConnect: Returning false because SSL_ConnectAndVerify failed

I125: CnxConnectAuthd: Returning false because CnxAuthdConnect failed

I125: Cnx_Connect: Returning false because CnxConnectAuthd failed

I125: Cnx_Connect: Error message:

I125: VMClient_ConnectMksClientEx - Remote socket connection failed.

I125: VMClient_ConnectMksClientEx - trying local socket connection to /vmfs/volumes/guid/vmnamefolder/vmname.vmx

I125: VMClientConnectSocketEx

I125: CnxAuthdConnectPipe: Returning false because we ran out of retries when CreateFileW

I125: CnxAuthdConnect: Returning false because CnxAuthdConnectPipe failed

I125: CnxConnectAuthd: Returning false because CnxAuthdConnect failed

I125: Cnx_Connect: Returning false because CnxConnectAuthd failed

I125: Cnx_Connect: Error message: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period

I125: VMClient_ConnectMksClientEx - Local socket connection failed.

I125: cui::MKSVMDB::OnSetAttachError (448E010): -44

I125: DlgUI: Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period.

I can connect from my computer to 902 port of esx server.

Kind regards

Nenad

Reply
0 Kudos
venugs
Enthusiast
Enthusiast

Were you able to solve the issue?

how about port 902? telnet works?

Reply
0 Kudos
CNenad
Contributor
Contributor

Hi Venugs

No, I did not solve issue Smiley Sad

I wrote in previous reply: "I can connect from my computer to 902 port of esx server"

Regards

Nenad

Reply
0 Kudos
CQuartetti
Hot Shot
Hot Shot

I can't think of an obvious cause so far. Some more ideas to check:

  • Double check which VMRC.exe executable you're launching. PowerCLI has its own copy. If you've installed VMRC 10 with the .msi installer and default options, you should be running the one in C:\Program Files (x86)\VMware\VMware Remote Console.
  • Do you see this problem if you log in as a different user on the same computer?
  • It looks like a local issue--I assume it happens for all ESX servers you've tried?
Reply
0 Kudos
CNenad
Contributor
Contributor

Hello

Sorry for late answer Smiley Sad because I was on vacation Smiley Happy

I have checked and there is only one vmrc.exe on default path installed from MSI: C:\Program Files (x86)\VMware\VMware Remote Console

I have create new account / profile, logged on into same computer and try only from Web Console after choosing VM and click onto launch remote console from summary tab.

Same error: Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period.

I have checked console version and it was 10.0.0 build-5606693 so I was checked for updated version and installed last one: 10.0.1 build-5898794 and tried once again.

Same error: Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period.

Smiley Sad

I have also trying to run vmrc.exe from command line passing vmrc url:

C:\Program Files (x86)\VMware\VMware Remote Console>vmrc vmrc://esxvc6.domain.tld:443/?moid=vm-490

Same error: Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period.

Just installed on new Windows 7 computer VMRC 10.0.1 and same error with few different users.

It is possible some kind of problem with certificate because on first vmrc run I've got message about invalid security certificate and turn on check box: always trust this host with this certificate (it is virtual centre 6) and click onto connect anyway button.

Freezed, confused Smiley Happy

Kind regards

Nenad

Reply
0 Kudos
CQuartetti
Hot Shot
Hot Shot

Lets investigate this line from your log next:

I125: SSL Error: error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol

Things to do:

  • Check your server's TLS settings versus the client's and make sure they're compatible.
  • Check or post the relevant entries from the server's hostd log when you attempt to connect.
  • Post more context from your VMRC log from before the MKS failure.
Reply
0 Kudos
CNenad
Contributor
Contributor

Hello,

My coworker from ESX team gave me this tail-ed log from hostd:

2017-07-21T12:09:46.951Z [56E81B90 verbose 'SoapAdapter'] Responded to service state request

2017-07-21T12:09:54.498Z[57982B90 verbose 'SoapAdapter'] Responded to service state request

2017-07-21T12:10:00.595Z[5699CB90 info 'Vmsvc.vm:/vmfs/volumes/5044ba26-5248d8e8-098a-001a4bff2131/VMNAME/VMNAME.vmx' opID=7c8e92eb-ab] Ticket issued for mks service to user: vpxuser

2017-07-21T12:10:01.846Z [57982B90 verbose 'SoapAdapter'] Responded to service state request

2017-07-21T12:10:16.952Z [56181B90 verbose 'SoapAdapter'] Responded to service state request

And log from VMRC client is attached as txt file.

Kind regards

Nenad

Reply
0 Kudos
CQuartetti
Hot Shot
Hot Shot

Please post hostd log activity at the same timestamps that you're seeing the SSL error in the local VMRC log.

Another idea which may give us more information: Log in to the ESX web client and launch VMRC from there and see if your results vary. Access it from a URL like <https://your-esx-server/ui>. You

Reply
0 Kudos
MikeFTS
Contributor
Contributor

See my post from another thread to enable the use of TLS 1.0 in VMRC 10:

https://communities.vmware.com/message/2702806#2702806

That might help you

Reply
0 Kudos