Posted   by 

Vmware Converter Could Not Start Service Vstor2 Programs

  1. Vmware Converter Could Not Start Service Vstor2 Programs Free
  2. Vmware Converter Could Not Start Service Vstor2 Programs For Kids
  3. Vmware Converter Could Not Start Service Vstor2 Programs Free
  4. Vmware Converter Could Not Start Service Vstor2 Programs Available
  5. Vcenter Converter Could Not Start Service
Last week, I was migrating some physical servers to VMware Server images with VMware Converter tool. I was using the latest and improved version of VMware Converter (v3.0.3 - Build 89816). I had two servers to migrate: one SBS 2003 server and one Windows 2003 based Terminal Server. I had to run the converter on a third piece of hardware while the servers were up and running, installing the converter agent service on them (AKA 'hot clone'). SBS server had two volumes, and the total used disk space was around 40GB. Terminal Server had two volumes and used disk space was around 25GB. Service

Vmware Converter Could Not Start Service Vstor2 Programs Free

First P2V migration session ran approximately for 6 hours on the SBS server and completed without any problems. I started the second session on the Terminal Server and checked the status every hour.
If you are familiar with the P2V process, you probably know that the tool initially creates the vmdk files, then fills them in with the files from the source machine (Cloning Phase). When all files are transferred to the virtual disks (vmdk files), then final step is called 'conversion'. At this stage, the storage, HAL and network specific driver files and their configuration gets modified. This step is necessary, otherwise the virtual disk will not be able to boot.
Anyhow, after running for 3 hours and 30 minutes, my Terminal Server P2V migration session failed at 99% with 'Unknown Error'! A quick Google search revealed that the 97% and 99% range belongs to Customization/Reconfig phase, meaning that it failed at the 'conversion' step. VMware converter has the ability to manually run the 'conversion'. I selected the newly created virtual machine as the source, and ran the 'Conversion Wizard', but the process failed again. This time, I decided to examine the log files to see what's wrong. Converter creates log files in two locations: Converter Console log files reside in user's profile folder (in my Vista laptop, they are located at: '%userprofile%AppDataLocalTemp'). Converter Agent log files reside in 'WindowsTemp' folder. After a quick review, I realized that the log files in the profile folder did not provide the detail level I needed. Then after going through the log files in 'WindowsTemp' (vmware-converter-n.log) I found what I was looking for:
[#2] [2008-08-23 07:33:53.707 'App' 3932 verbose] [registryUpdate,73] Applying registry update S_SYMMPI
[#2] [2008-08-23 07:33:53.708 'App' 3932 verbose] [registryHiveProxy,176] Saving registry key ControlSet001Servicessymmpi to .vstor2-p2v30-B4BDB4BD007E00000000000003000000WINDOWS$Reconfig$ControlSet001-Services-symmpi-reg
[#2] [2008-08-23 07:33:54.174 'App' 3932 verbose] [registryHiveProxy,152] Restoring registry key ControlSet001Servicessymmpi from C:Program FilesVMwareVMware Converterdata52-S_SYMMPI
[#2] [2008-08-23 07:33:54.202 'App' 3932 verbose] [fileUpdate,69] Update File system32driverssymmpi.sys
[#2] [2008-08-23 07:33:54.202 'App' 3932 verbose] [volumeProxy,95] Checking if WINDOWSsystem32driverssymmpi.sys exists...
[#2] [2008-08-23 07:33:54.205 'App' 3932 verbose] [volumeProxy,102] WINDOWSsystem32driverssymmpi.sys does not exist!
[#2] [2008-08-23 07:33:54.223 'App' 3932 error] [fileUpdate,120] Unable to find symmpi.sys in the specified CAB files
[#2] [2008-08-23 07:33:54.250 'App' 3932 info] [imageProcessingTaskStep,194] UfaSysReconfig::task{1}::task{2} step 'applying reconfigurations' destroyed

The Converter was failing at a specific file, symmpi.sys! Because it was looking for the file in 'WINDOWSsystem32drivers' folder, failing to find it there, then aborting the process. Another Google search revealed that this was the LSI Logic Miniport Driver file. Luckily, I found the same file in one of my other virtual machines, in the 'WINDOWSsystem32drivers' folder. To copy the file to my failing virtual Terminal Server, I connected its C: drive as an additional disk to my old virtual machine. After this, I could easily add a drive letter to the drive and was able copy the file.
I shutdown my old virtual machine, removed the drive connection. Then I ran the 'conversion Wizard' one more time selecting the new virtual Terminal Server as the source. The 'Conversion Wizard' only ran for a couple of minutes, then completed successfully. After this step, I was able to verify that I could successfully boot my new virtual Terminal Server.
My Google searches during this troubleshooting period showed me that this is a very common error. I spent about 2 hours and 30 minutes to find the solution and I hope this post can speed up your troubleshooting process. Please use the comments link below if you have any questions.

You can install Converter Standalone on a physical or a virtual machine. You can also modify or repair a Converter Standalone installation.

VMware Consolidated Backup Support for VMware Consolidated Backup (1026945) Date Published: 8/31/2010 VMware Converter The Vstor2 UFA Virtual Storage Driver service fails to start (1023795) Date Published: 9/3/2010 VMware Data Recovery Unable to access destination store after increasing it in VMware Data Recovery 1.2 (1024210) Date Published: 9/1/2010 VMware ESX Degraded performance on. The process known as VMware Virtual Storage Volume Driver or Vstor2 WS60 Virtual Storage Driver belongs to software VMware Converter Hosted or VMware Workstation by VMware (www.vmware.com). Description: Vstor2-ws60.sys is not essential for the Windows OS and causes relatively few problems. The vstor2-ws60.sys file is located in a subfolder of.

Vmware Converter Could Not Start Service Vstor2 ProgramsVmware

Vmware Converter Could Not Start Service Vstor2 Programs For Kids

The Local setup installs the Converter Standalone server, Converter Standalone agent, and Converter Standalone client for local use.

Note: Local installation of Converter Standalone complies with the following security restrictions:
  • After the initial setup, the use of an administrator account requires physical access to the product.
  • You can manage Converter Standalone only from the machine where it is installed.

Vmware Converter Could Not Start Service Vstor2 Programs Free

During the client-server installation, you can select the Converter Standalone components that you want to install on your system. You can also choose to join the Customer Experience Improvement Program. See Configuring the Customer Experience Improvement Program

Vmware Converter Could Not Start Service Vstor2 Programs Available

When you install the Converter Standalone server and Remote access, the local machine becomes a server for conversions, which you can manage remotely. When you install the Converter Standalone server and the Converter Standalone client, you can use the local machine to access remote Converter Standalone servers or create conversion jobs locally.

Vcenter Converter Could Not Start Service

If you install only Converter Standalone client, you can connect to a remote Converter Standalone server. You can then use the remote machine to convert hosted virtual machines, managed virtual machines, or remote physical machines.