This known issue occurs when the Data Migration Tool is run against a vCenter Server with MS SQL Express that has been updated (for example, if vCenter Server 4.0 is updated to Update 2 or if vCenter Server 2.5 is updated to vCenter Server 4.0.)
When vCenter Server is upgraded, the value of the following registry keys are switched from Bundled to Custom:
•In Windows 2003 – HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter\DbServerType
•In Windows 2008 – HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VirtualCenter\DbServerTypeThe database migration tool fails to properly backup the database when this value is set to Custom, even though there are no observable error messages displayed. If the value is manually changed back to Bundled, then the database tool properly backs up and restores the database to the vCenter Server 4.1 machine. The backup part of the script checks if the DSN forwards to a localhost or a remote location to determine if the database is local or not. However, the Custom value is used by the restore part of the script which considers that the database is remote and does not restore the database dump created by the backup part.
Changing the registry value from Custom to Bundled before launching the backup.bat script resolves this issue. If you have already gone through the database migration, you can still resolve this issue by performing these steps after making the registry change.
To change the registry value from Custom to Bundled:
1.On the machine you are trying to perform the backup, go to Start > Run, type regedit, and click OK.
2.For Windows 2003 navigate to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter or for Windows 2008 navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VirtualCenter.
3.Right-click the DbServerType value in the right hand pane, and click Modify.
4.Change the value from Custom to Bundled, and click OK.
5.Launch the backup.bat script as normal.
6.Ensure that vCenter Server is not already installed on the target server. If it is installed, uninstall it. If you do not uninstall it, the installation process fails.
7.Launch install.bat and follow the Installation Wizard.
Thursday, December 30, 2010
Tuesday, December 07, 2010
vSphere Client Error parsing the server “SERVER IP” “clients.xml” file. Login will continue, contact your system administrator
This is solution for xml error
Remove this KB980773 seems to have undesired effect on MS DotNet Framework required by the VMware vSphere client to run. I believe we will have to wait for VMware to fix it or to push Microsoft to fix it
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 :
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.
Remove this KB980773 seems to have undesired effect on MS DotNet Framework required by the VMware vSphere client to run. I believe we will have to wait for VMware to fix it or to push Microsoft to fix it
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 :
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.
Fault issues
Common Fault issues in VMware
Infrastructure
1007819 Dealing with an unresponsive virtual machine | 1007802 Confirming a virtual machine is unresponsive 1007808 Ensuring a virtual machine is not inaccessible due to a VMware VirtualCenter issue 1007818 Dealing with unresponsive guest OS issues | 1007805 Locating a virtual machine log files on an ESX host 1007813 Troubleshooting a virtual machine that has become unresponsive because of an ESX host | 1000674 Can't stop or kill virtual machine 1007813 Troubleshooting a virtual machine that has become unresponsive because of an ESX host | 1004344 Identifying causes of not being able to power cycle ESX Server virtual machines 1007814 Troubleshooting a virtual machine that is unresponsive because of configuration issues | ||
1007808 Ensuring a virtual machine is not inaccessible due to a VMware VirtualCenter issue | 1003895 Stopping, starting, or restarting the VirtualCenter Server service | 1002687 Virtual machine stops responding in a Power On state in VirtualCenter | 7114568 Cannot Power on Virtual Machines, "Not enough licenses installed to perform operation" Error Message | 1004592 Vmware VirtualCenter console displays handshake error. | ||
1007813 Troubleshooting a virtual machine that has become unresponsive because of an ESX host | 1003751 Verifying that ESX virtual machine storage is accessible 1003659 Identifying shared storage issues with ESX 3.x 1004005 [Internal] Third Party System Management agents in the Service Console | 1004144 ESX Server virtual machines stop responding due to shared storage connectivity issues 1006791 Server stops responding and shows errors on a purple screen | 1003755 Verifying sufficient free disk space for an ESX virtual machine 10051 Virtual machine does not power on because of missing or locked files | 1003564 Investigating disk space on an ESX host 1003690 Ensuring your hardware is functioning correctly | ||
1007814 Troubleshooting a virtual machine that is unresponsive because of configuration issues | 1005734 Troubleshooting a virtual machine that stops responding or fails when the CD-ROM entry is ATAPI 1003164 Guest stops responding after connecting a USB CD-ROM | 1001637 Virtual machine does not power on and there is high CPU reservation | 1002025 Virtual machine stops responding during backup | 1002836 Why snapshot removal can stop a virtual machine virtual machine for long time | ||
1007818 Dealing with unresponsive guest OS issues | 1004007 Investigating operating system disk space | 1007577 Do not use guest OS performance tools to monitor virtual machine performance | 1007866 Using Windows Event Viewer to identify the cause of an unresponsive or failed virtual machine | 1004764 Unable to shutdown Windows using Shutdown Guest option | ||
Subscribe to:
Posts (Atom)