• Vmware Converter Could Not Start Service
• Start Service From Command Line

Hi,

., I have noticed by vCenter that VMware is not working. When I want to start. VMware vCenter Converter. Not start VMware vCenter Converter Standalone.

Trying to install 'vCenter Converter', the installer fails with this error:

Vmware Converter Could Not Start Service

1. Driver service failed to start due to the. Removes the vstor2.sys file, but does not remove the. V) was marked as physical 'Disk 1', with a drive that was added to the system later (data drive), marked as physical 'Disk 0'.
2. May 29, 2018 - 0 Comments. Error 1053 Could Not Start Service Vmware Converter Could Not Start Service Vstor2 Programs. Attention, Internet Explorer User.

- Error -> 'Error 29142: Could not start service Vstor2 MntApi 2.0 Driver (shared)'

- Event Viewer -> 'The Vstor2 MntApi 2.0 Driver (shared) service failed to start due to the following error: A device attached to the system is not functioning'

Environment is:

Start Service From Command Line

- Physical Machine: HP Compaq nw8440 ( laptop )

- Operating System: Windows XP Professional SP3

- Run 'vCenter Converter' installer using 'Administrator' account

There is nothing attached to the laptop when I try to install 'vCenter Converter'

I tried:

- Several versions of 'vCenter Converter' from 4.3.0 to 5.5.3 ( all of them supporting installation in Windows XP ) -> Same error

- Uninstall / Reinstall USB ports ( USB Root Hub ) in the Physical Machine -> Same error

- Restart several times the Physical Machine -> Same error

Attached is the log file the installer generated ( invoking the installer: VMware-converter-all-5.5.0-292238.exe /v'/l*v VMwareInstall.log' ) -> Search for: '29142'

Any idea?

Thanks

Hi Reuben,

Try going back to version 5.5 and disable the Converter's use of SSL:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&external...

Its just one file you need to edit and should bring the time for conversion down to hours, assuming that SSL was the problem. Another thing that might help is to disable any services on the Server 2003 box. Also, disabling VSS can also help a LOT:

http://www.vladan.fr/how-to-disable-ssl-encryption-in-vmware-vcenter-converter-standalone-to-speed-u...