[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2482
  • Last Modified:

VM Console: vSphere client and VIClient at the same time

Hi,

I have the following problem:
I have a Client machine with .NET 4.0.
This client has to connect to a VMware Virtual Center 2.5 as well as to a vSphere Environment.

VMware states that the vSphere client is backward compatible. Means, that it also can connect to VMware Virtual Center 2.5 Servers.
When I install the vSphere client, I can connect without any problem to the vSphere environment and open a console of a virtual machine.

When I'm trying to connect to the VMware Virtual Center server, I'm prompted to install a vSphere client upgrade, which I do. Other wise I can't connect.
When I'm connected with the vSphere Client to the VMware Virtual Center server, I can't open the console of virtual machines.
The error message is:
Exception has been thrown by the target of an invocation

It is described here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004281

I already tried the solution of the KB article, with no luck.
Also, I found this hint in the internet:
copy libeay32.dll and ssleay32.dll from C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\2.5 to C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher.
Tried it, without luck.

Additional information:
I observed that it doesn't matter on which ESX the VM I'm trying to connect resides. DNS resolution is working fine.

Do you have any idea?
Thanks and kind regards.
0
fr0nk
Asked:
fr0nk
  • 6
  • 4
1 Solution
 
coolsport00Commented:
What you're specifically needing is the Compatibility Matrix Guide "fr0nk":
http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf

As you can see on pg. 3, the Client is NOT backwards compatible. There is no way around this. The only thing you can do is manage 1 of your infrastructures with the Client and the other via web access. Or, you need to simply manage from 2 workstations...1 having the VI Client and 1 having the vSphere Client.

Regards,
~coolsport00
0
 
fr0nkAuthor Commented:
Thanks for your input.
The "Client Upgrade" that is offered my vsphere client when connecting to the Virtual Center server actually builds up a new directory ("2.5") inside the installation path of the VI Client besides the "4.1" folder.

So I assume I can't connect to the Virtual Center Server with the 4.1 Client but with the 2.5 client that seems to be installed "side by side" during the update with the 4.1 one.

Kind regards.
0
 
coolsport00Commented:
Correct; you have to use VI Client for Virt Ctr 2.5 and vSphere Client for 4.x. For us admins, it's a real hassle. I actually had it out with a support engr about this several mos back about the lack of backwards compatibility....quite cumbersome!

~coolsport00
0
Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

 
fr0nkAuthor Commented:
Thanks for your input,
Then I have to re-phrase the question: How do I install the clients side by side?
When both clients are installed side by side there remains only one executable, but 2 subfolders ("4.1" and "2.5"in the installation directory. I haven't figured out how to start one of the clients in particular.

Kind regards
0
 
coolsport00Commented:
Oh...ok...I misunderstood. You can't...not on the same workstation as I mentioned above. You have to install on separate workstations.

~coolsport00
0
 
coolsport00Commented:
Looks like someone experienced the same issue. There "may" be a way to do what you need (see 'bgoering's' solution):
http://www.experts-exchange.com/Software/VMWare/Q_26618598.html?sfQueryTermInfo=1+10+30+client+vsphere

~coolsport00
0
 
fr0nkAuthor Commented:
Thanks for the hint. I'm still confused why both clients doesn't work at the same time.
0
 
coolsport00Commented:
VMware design...non-compatibility between client/host/vCenter versions. I can't answer anything more in detail as it's more of a design/developer issue. I do feel your frustration though...

Regards,
~coolsport00
0
 
fr0nkAuthor Commented:
No, I mean you provided the PDF with the compatibility matrix. That wasn't my point. My point was: when there's incompatibility with connecting vSphere Client <-> Virtual Center 2.5, and an update is offered, both clients seem to be installed side-by-side. But there's only one executable which starts the vSphere client. Confusing stuff... ;-)

Kind regards.
0
 
coolsport00Commented:
Ah...I see. Yes....tis true. :)

~coolsport00
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now