解决windows2003下无法使用VMware vSphere Client

20100826更新:有些朋友遇到此问题可能是微软的某补丁造成的,解决这个补丁问题,请查看本文下半部分!卸载该补丁见下图:

kb980773.jpg

大小: 88.9 K
尺寸: 300 x 168
浏览: 326 次
点击打开新窗口浏览全图

记得将系统更新补丁功能调整为非自动,不然卸载后很快又会自动安装回去(经测试发现卸载后2天自动安装了),具体调整为:右键点击“我的电脑”->“属性”->“自动更新”->选择第三个选项->确认完成。


最近几天在我indows2003服务器上登陆安装在本机的VC(VirtualCenter server)总是遇到如下问题:

  1. 先弹出无法连接的错误框:“分析服务器"clients.xml"文件时出错。登录将继续,请联系系统管理员”。
  2. 点击确定继续弹出错误框:“VirtualInfrastructure.Utils.HttpWebRequestProxy的类型初始值设定项引发异常。”
  3. 再次点击“确定”后返回登录窗口:显示“连接失败”。

而安装在本机(windows 2008)的VMware vSphere Client却可以顺利登陆VC,这让我想起来之前遇到过在服务器上无法登陆,却可以在别的电脑上安装客户端登陆。那么问题应该出在客户端身上才是。我将现有的客户端进行了卸载,然后重新安装,无法解决。(这里我要告诉各位:windows服务器有个很大的特点,那就是遇到问题先重启试试看,或许就有效,而我却没第一时间去重启,囧~或许我重启一下,问题解决也不用走下面这么多弯路,当然,如果你重启后没效果,请继续往下看!)

上google查阅了错误信息,都是一篇在windows7下的解决方案的复制再复制。如果有朋友用windows7安装客户端遇到无法连接的问题,可以点击此处去看解决方案。

回到问题,虽然网上的资料没给我直接的解决之道,但是却给了我启发,问题很大程度上应该出在.net上。客户端是依赖微软的.net架构运行的,而现在的.net可能出问题了。我下载了清除之前.net版本的工具将本机的.net进行清除以便于我重新安装.net 2.0

清理完成后重启,新的问题出现了。服务中的VMware VirtualCenter Management Webservices服务却没有启动,之前也出现过这个问题,每次手动启动即可。而这次多次尝试后依然没法启动,我变查看日志,查看与该服务相关的服务是否有问题。

与VMware相关的服务如下:

  1. SQL Server (SQLEXP_VIM)
  2. VMware vCenter Converter
  3. VMware vCenter Orchestrator Configuration
  4. VMware VirtualCenter Management Webservices
  5. VMware VirtualCenter Server
  6. VMwareVCMSDS

我依次启动了1、5服后,成功启动了4服务,也就说明,VC服务依赖数据库,而VC管理服务依赖于VC服务。

完成服务启动,我顺手打开VMware vSphere Client却弹出来初始化失败,忘记装.net 2.0了。将.net 2.0安装好后,再次登陆,稍等片刻,登陆成功!问题解决。


下半部分 来源:http://thinklog.blog.163.com/blog/static/71896182201061295159614/

使用vsphere 客户端连接vpshere 服务器时,跳出窗口,提示:分析服务器“X.X.X.X”的“clients.xml”文件时出错。从网上看到,是由于.NET 自动升级造成的。修改方法是删除升级的补丁(980773),然后将自动升级更改为“安装时提示我”,然后在升级时忽略掉这个升级包。

vSphere Client does not open on any Windows operating systems with the error: parsing the server "<servername>" "clients.xml" file
注:2010.6.9 微软更新了.net framework。可能是load .net framework的工作机制改变了,
Symptoms
·        When trying to launch the vSphere Client you receive errors similar to:
Error parsing the server "<servername>" "clients.xml" file.
The type initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy' threw an exception.
Resolution
You cannot use vSphere Clients prior to the Update 1 release, to access the vCenter Server or ESX hosts because of a Microsoft update that targets the .NET Framework (980773), released on June 9th 2010.  
 
Perform one of these two options to correct the issue:
1.    Download and install vSphere Client 4.0 Update 1 (build 208111) or Update 2 (build 258672) using method a or b below, depending on your environment.
a.    To download and install the vSphere Client for ESX, ESXi (paid version), and vCenter Server:
                                       i.        Go the downloads site.
Note: The vSphere Client .exe is part of the ESX, ESXi, or vCenter Server download binaries.
                                      ii.        Click Download next to your ESX, ESXi, or vCenter Server edition.
                                     iii.        Log in with your VMware Account credentials.
                                     iv.        Click Yes to agree to the EULA.
                                      v.        Click the .exe link next to vSphere Client and Host Update Utility.
Note: You do not need to download the entire vSphere suite, only the vSphere Client.
                                     vi.        Follow the on-screen instructions to install the updated vSphere Client.
b.    To download and install the vSphere Client Update 1 for ESXi (free version):
                                       i.        Go to the ESXi download site.
                                      ii.        Click Download.
                                     iii.        Log in with your account credentials, or register for free.
                                     iv.        Click Download next to vSphere Client and Host Update Utility.
                                      v.        Follow the on-screen instructions to install the updated vSphere Client.
2.    Remove the MS update from your Windows operating system. The vSphere Client works after the update is removed.
Note: This affects Windows XP, Windows 2003, Windows 2008, Windows Vista, and Windows 7.
 If the build number for your vSphere Client is 208111 or higher, then you have vSphere Client Update 1 or later, and should not be affected by this issue.
 
You can determine the version of vSphere Client by reviewing the build number located in the first line of a viclient.log file, located in %USERPROFILE%\Local Settings\Application Data\VMware\vpx on the system running the vSphere Client if the OS is Windows XP or 2003 and %USERPROFILE%\AppData\Local\VMware\vpx in 64 bit Windows 7 or 2008. Build 208111 or higher indicates you are using vSphere Client 4.0 Update 1 or later.
For example:
2010-05-19 03:08:58.508  Log for vSphere Client Launcher, pid=4756, version=4.0.0, build=build-208111, option=release
-------------------------------------------------------------------------------------------------------
 当然如果你不想升级vSphere Client也不是没有其他办法。见下面方法,同样来自官方。
This issue is resolved in VMware vSphere 4.0 Update 1. Prior to this update, the vSphere Client is not supported in Windows 7 or Windows 2008 R2 and it does not run in Compatibility Mode. This issue may occur because of the .NET loading mechanism change in Windows 2008 R2 and Windows 7.
 
You can download and install the VMware vSphere 4.0 Update 1 from the download page.
 
If you cannot upgrade to VMware vSphere 4.0 Update 1, there are 2 possible workarounds. Perform one of these options:
·        Using VMware Player or VMware Workstation, install a Windows XP virtual machine in Windows 7 or Windows 2008 R2.
·        Bypass the normal .NET Framework loading mechanism.
Warning: This workaround is unsupported.
To bypass the normal .NET Framework loading mechanism:
1.     Download the file system.dll. This file is typically located in  %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\ directory of a non-Windows 7 or Windows 2008 R2 machine with .NET v3.5 SP1 installed.
2.     Copy the file to C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib.
Note: If the lib directory does not exist, create it.
 
3.     Open VpxClient.exe.config in a text editor. The file is located at C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher.
4.     Add the following three lines to VpxClient.exe.config, just before </configuration>:
<runtime>
<developmentMode developerInstallation="true"/>
</runtime>
 
5.     From Windows 2008 R2 or Windows 7 System Properties, click the Advanced tab > Environment Variables
6.     Create a new System variable called DEVPATH and assign the value:
C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
Note: For 32bit operating systems, replace Program Files (x86)with Program Files.
You can now launch vSphere Client from a Windows 7 or Windows 2008 R2 machine. You may have to right-click on the vSphere Client icon and choose 
Run as administrator.

 

Tags: vmware, vsphere

上一篇: 端午节快乐 博客PR升为2
下一篇: Linux或Unix下怎样修改系统时间

相关文章

发表评论