Return to site

Vmware Converter Could Not Start Service Vstor2 Programs

broken image


  1. Vmware Converter Could Not Start Service Vstor2 Programs Available
  2. Vmware Standalone Converter Could Not Start Service

After installing vCenter Server Standalone, you experience these symptoms:

  • The VMware Converter Standalone Server service fails to start
  • Starting the VMware Converter Standalone Server service fails with the error:
    Cannot start the VMware Converter Standalone Server service
  • In the vmware-converter-server.log file, you see errors similar to:
    [02804 info 'Locale'] Locale subsystem initialized from C:Program Files (x86)VMwareVMware vCenter Converter Standalonelocale with default locale en.
    [02804 warning 'Locale'] Locale ' not supported in module 'iso2win'.
    [02804 error 'Default'] [user,249] Invalid server locale specified.
    [02804 info 'Default'] CoreDump: Writing minidump
    [02804 panic 'Default']
Vmware Converter Could Not Start Service Vstor2 Programs

Dec 28, 2018 Additionally, Event ID 7009 can be get in Windows event viewer with content A timeout was reached (30000 milliseconds) while waiting for the VMware vCenter Converter Standalone Worker service to connect. This issue caused by Service Control Manager generates an event if a service does not respond within the defined timeout period (the default. Converter Standalone agent does not start automatically after reboot If the source machine starts up too slowly, Converter Standalone agent might not start automatically after the source machine is restarted. Workaround: Start the Converter Standalone agent manually: Right-click My Computer and select Manage.

Usually, when you use a virtualization solution, you create the virtual machines from this program and you install the operating system there.

However, thanks to VMware Workstation and their VMware vCenter Converter Standalone product, you can also virtualize a physical PC to turn it into a virtual machine.

1. Install VMware vCenter Converter Standalone

To get started, open the 'File' menu of VMware Workstation and click : Virtualize a Physical Machine.

If VMware vCenter Converter Standalone is not installed on your computer, this message will be displayed :

Plain Text

Click on the link provided and you will come to the 'Download VMware vCenter Converter Standalone 6.2' page.
Create a free account on VMware or connect with yours if you already have one by clicking the 'Download Now' button.

Then, run the downloaded 'VMware-converter-en-6.2.0-8466193.exe' file.

The VMware vCenter Converter Standalone installation wizard appears.

Accept the license agreement.

Choose : Client-Server installation (advanced).

As you can see, several components will be installed :

Vmware Converter Could Not Start Service Vstor2 Programs

Vmware Converter Could Not Start Service Vstor2 Programs Available

  • Converter server : centralizes conversion management
  • Remote access : allows access to the remote conversion server
  • Converter agent : allows you to convert the current PC (and thus to choose it as a source) into a virtual machine
  • Converter client : this client connects to the conversion server and provides a graphical interface to manage conversions

Then, you will see that VMware vCenter Converter Standalone will use 3 different ports :

  • HTTPS Service Port : 433
  • HTTP Service Port : 80
  • Agent Service Port : 9089

The small problem is that if you want to install VMware vCenter Converter Standalone on the same computer as VMware Workstation, you may receive the 'Port 443 is already in use' error.

If so, go to VMware Workstation's 'Shared VMs' section and disable VM sharing.
To do this, click on 'Change Settings' then on : Disable Sharing.
OR change the port shown here so that the VMware Workstation Server doesn't conflict with VMware vCenter Converter Standalone.

Important : since version 16 of VMware Workstation, this feature no longer exists, but the associated 'VMware Workstation Server' service (which corresponds to the 'vmware-hostd.exe' process) still exists and is configured to start automatically when Windows starts up .
You can therefore no longer disable this sharing of virtual machines in the settings of VMware Workstation.

To solve the problem with this new version of VMware Workstation, you have 2 possibilities.
The 1st solution is to open notepad as administrator and edit this file : C:ProgramDataVMwarehostdproxy.xml
In this file, change the line '<httpsPort>443</httpsPort>' to '<httpsPort>-1</httpsPort>'.
Then, restart the 'VMware Workstation Server' service from Windows.

Not

Source : [BUG] Service uses port 443

The 2nd solution is to stop the 'VMware Workstation Server' service and change the startup type to 'Disabled'.
This is what happened when you turned off virtual machine sharing in older versions of VMware Workstation.
As a reminder : this service has become unnecessary since this feature has been retired from VMware Workstation.

Join the VMware Customer Experience Improvement Program (CEIP) if you wish.

Vstor2

Click Install.

Wait while installing VMware vCenter Converter Standalone.

Vmware Converter Could Not Start Service Vstor2 Programs

Dec 28, 2018 Additionally, Event ID 7009 can be get in Windows event viewer with content A timeout was reached (30000 milliseconds) while waiting for the VMware vCenter Converter Standalone Worker service to connect. This issue caused by Service Control Manager generates an event if a service does not respond within the defined timeout period (the default. Converter Standalone agent does not start automatically after reboot If the source machine starts up too slowly, Converter Standalone agent might not start automatically after the source machine is restarted. Workaround: Start the Converter Standalone agent manually: Right-click My Computer and select Manage.

Usually, when you use a virtualization solution, you create the virtual machines from this program and you install the operating system there.

However, thanks to VMware Workstation and their VMware vCenter Converter Standalone product, you can also virtualize a physical PC to turn it into a virtual machine.

1. Install VMware vCenter Converter Standalone

To get started, open the 'File' menu of VMware Workstation and click : Virtualize a Physical Machine.

If VMware vCenter Converter Standalone is not installed on your computer, this message will be displayed :

Plain Text

Click on the link provided and you will come to the 'Download VMware vCenter Converter Standalone 6.2' page.
Create a free account on VMware or connect with yours if you already have one by clicking the 'Download Now' button.

Then, run the downloaded 'VMware-converter-en-6.2.0-8466193.exe' file.

The VMware vCenter Converter Standalone installation wizard appears.

Accept the license agreement.

Choose : Client-Server installation (advanced).

As you can see, several components will be installed :

Vmware Converter Could Not Start Service Vstor2 Programs Available

  • Converter server : centralizes conversion management
  • Remote access : allows access to the remote conversion server
  • Converter agent : allows you to convert the current PC (and thus to choose it as a source) into a virtual machine
  • Converter client : this client connects to the conversion server and provides a graphical interface to manage conversions

Then, you will see that VMware vCenter Converter Standalone will use 3 different ports :

  • HTTPS Service Port : 433
  • HTTP Service Port : 80
  • Agent Service Port : 9089

The small problem is that if you want to install VMware vCenter Converter Standalone on the same computer as VMware Workstation, you may receive the 'Port 443 is already in use' error.

If so, go to VMware Workstation's 'Shared VMs' section and disable VM sharing.
To do this, click on 'Change Settings' then on : Disable Sharing.
OR change the port shown here so that the VMware Workstation Server doesn't conflict with VMware vCenter Converter Standalone.

Important : since version 16 of VMware Workstation, this feature no longer exists, but the associated 'VMware Workstation Server' service (which corresponds to the 'vmware-hostd.exe' process) still exists and is configured to start automatically when Windows starts up .
You can therefore no longer disable this sharing of virtual machines in the settings of VMware Workstation.

To solve the problem with this new version of VMware Workstation, you have 2 possibilities.
The 1st solution is to open notepad as administrator and edit this file : C:ProgramDataVMwarehostdproxy.xml
In this file, change the line '<httpsPort>443</httpsPort>' to '<httpsPort>-1</httpsPort>'.
Then, restart the 'VMware Workstation Server' service from Windows.

Source : [BUG] Service uses port 443

The 2nd solution is to stop the 'VMware Workstation Server' service and change the startup type to 'Disabled'.
This is what happened when you turned off virtual machine sharing in older versions of VMware Workstation.
As a reminder : this service has become unnecessary since this feature has been retired from VMware Workstation.

Join the VMware Customer Experience Improvement Program (CEIP) if you wish.

Click Install.

Wait while installing VMware vCenter Converter Standalone.

At the end of the installation, it's possible that a warning 'Could not start service' appears.

If so, go to Windows Services and look for the 'VMware vCenter Converter Standalone Agent' service in the list and start it.

Always if you had this warning, restart the installation of VMware vCenter Converter Standalone and choose the option 'Repair' if these choices are available.

Once installed, uncheck the 'Run Converter Standalone Client now' box and click Finish.

2. Virtualize the physical PC from VMware Workstation

To virtualize your physical PC where you just installed VMware vCenter Converter Standalone, launch VMware Workstation and click : File -> Virtualize a Physical Machine.

A 'Virtualize a Physical Machine' window appears.

Vmware Standalone Converter Could Not Start Service

Specify :

  • the name or IP address of the physical PC to virtualize (where you installed the vCenter Converter)
  • a user account with administrator rights on this computer
  • his password. Warning : the account must have a password, otherwise, it doesn't work.

Warning : as specified by VMware, you must have administrator rights on the desired machine and if this computer is running Windows Vista or later, you will also need to disable the Windows User Account Control (UAC).

If the error 'Permission to perform this operation was denied' appears, your account does not have administrator rights.

The easiest way to resolve this problem is to enable the 'Administrator' account present by default on Windows and add a password to this account.

To use the Administrator account, type this.

To do this, in the Windows Start menu, look for 'Account Control' and click 'Change User Account Control settings'.

Move the cursor all the way down (which is obviously not recommended by Windows) and click OK.

As Windows will tell you through the notifications, you will need to restart the computer for the user account control to be disabled.
Click on it and restart the computer.

Restart the previously launched wizard and click Next at this step.

Ignore the error caused by using VMware self-signed SSL certificates by checking the 'Always trust this host with this certificate' box and clicking : Connect Anyway.

Choose a name and location to store the virtual machine that will be created from your physical PC.
Note : P2V means Physical to Virtual.

Provide the same credentials as before for the network share.

If you had used the Administrator account at the previous step, reuse it here.

Wait during the virtualization process of your physical PC.
Note that this process can obviously take a lot of time depending on how much data is on your physical PC.

Different statuses will appear during this virtualization process :

  • Starting the virtualization of '[name of the physical PC]'
  • Copying the disk data of '[name of the physical PC]'
  • Configuring '[name of the physical PC]' as a new virtual machine

After a while, your virtual machine will appear in VMware Workstation.





broken image