ESXi

 View Only

  • 1.  vSphere client can not be started

    Posted Feb 15, 2010 11:42 AM

    I have been using ESXi4 with windows (Windows7) management software of vSphere client for long. When trying booting vSphere client for some reason, the system said something like "vpxClient stopped running. Trying to find a measure to treat against this incident" . And it never boot.

    When installing vSphere client at the first time of ESXi installation, I have add a sentence like

    <runtime>

    <developmentMode developerInstallation="true"/>

    </runtime>

    in the VpxClient.exe.config file.

    Also I have copied and pasted system.dll file into Program Files(x86）\vmware\Infrastructure\Virtual Infrastructure Client\Launcher\lib

    How can I reboot vSphere Client ?



  • 2.  RE: vSphere client can not be started

    Posted Feb 15, 2010 01:32 PM

    Update your ESXi with latest build. vSphere Client compatible with Windows 7 is also included.


    ---

    MCSA, MCTS, VCP, VMware vExpert '2009

    http://blog.vadmin.ru



  • 3.  RE: vSphere client can not be started

    Posted Feb 15, 2010 08:43 PM

    Hi, thanks for advice.

    I have updated and installed VMware-viclient-all-4.0.0-208111.exe and this solved ESXi boot troulbe. It no longer needed patch for Win 7.

    Thank you again.



  • 4.  RE: vSphere client can not be started

    Posted Feb 15, 2010 09:09 PM

    If you consider any comment as helpful, please award points :smileyhappy:


    ---

    MCSA, MCTS, VCP, VMware vExpert '2009

    http://blog.vadmin.ru



  • 5.  RE: vSphere client can not be started

    Posted Feb 16, 2010 09:21 AM

    Nice point :smileyhappy:

    iSCSI Software Support Department



  • 6.  RE: vSphere client can not be started
    Best Answer

    Posted Feb 15, 2010 02:34 PM

    Are you using the v4.0 update 1 version of the VSClient? it's the only one that's supported with W7.

    iSCSI Software Support Department



  • 7.  RE: vSphere client can not be started

    Posted Feb 15, 2010 08:50 PM

    Hi Thanks for your advice. As I have replied to Anton, upgrade to VMware-viclient-all-4.0.0-208111 has solved my trouble. Thank you again for your attention.