Name: same as source system, as detected by the converter The conversion wizard installs its agent and connects to it OK.ĭestination type: VMware Workstation or other VMware virtual machine Specifying the source system goes smoothly, though I ignore the certificate error. On starting the converter, I "Connect to a local server" I'm using VMware vCenter Converter Standalone client, v5.0.0 build-470252, running on a Windows 7 64bit computer, trying to import a running Windows 2008 virtual machine (hosted by VMWare infrastructure) onto my local box. Either way, network connectivity is fine, and I'm stumped as to why it keeps failing at this point. The conversion prompts for the key initially when the process starts, so I'm not sure if the "key can't be retrieved" error is as result of the "network unrechable" error, or if the key error comes first before the network error. It's up and running just fine, and I maintain a SSH connection the entire time, but for some reason this error keeps coming up and I'm not sure why.
(return code 2)ġ92.168.8.232 in this case is the source system. Then, at 3%, the conversion fails with this error:įAILED: A general system error occurred: connect (`192.168.8.232'): Network is unreachable connect (`192.168.8.232'): Network is unreachable connect (`192.168.8.232'): The conversion starts, connects to the helper, and starts formatting the destination. The wizard goes through smooth, and the source information is pulls down all looks correct. Running it on a Windows 7 system, and I'm attempting to convert a Linux system that's running CentOS6.
VMware vCenter Converter Standalone ServerĪs the subject notes, I'm trying to test out converting some physical systems to VMWare using Converter 5.5 Standalone. The service did not respond to the start or control request in a timely fashion. The VMware vCenter Converter Standalone Server service failed to start due to the following error:
Service fails to start in a timely fashion.
VMware vCenter Converter Standalone Server version 5.5.2 build-1890136 running under Windows 7 Pro 圆4.
Microsoft software shadow copy provider started manual hr = 0x80029c4a.Ĭom+ system application started automatic Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. Writer Id: and name VSSEvent cannot be started. Vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool I attached the converter logs and here is a bunch of info from the Exchange server.įAILED: Unable to create a VSS snapshot of the source volume(s). Now it makes it 1 minute in and then fails. The first time I ran the tool it made it to 94% and then failed with the error below. I am trying to convert my physical Exchange 2007 SP1 server running on 2003 server SP2 to ESXi.