Converter Standalone Agent Error Code 1603
Contents |
connection and IPSEC Services service fails to start ‘Cannot find the specifiedfile' Sophos Enterprise Console not updating. Error "An update manager unable to complete converter agent installation another version of this product is already installed has not updated since…" → VMware vCenter Converter Standalone error 1603 vmware converter error 1935 ‘Unable to complete vCenter Converter Agent installation' while trying to p2v +fix Tue-2011-08-02 1 Comment When doing
Vmware Converter Agent Download
a p2v I always use the standalone version of the Converter software. It proved to be more stable than the vCenter Converter plugin. While trying to p2v a https://kb.vmware.com/kb/1021465 server onto our vSphere platform I was presented with the following error by the VMware vCenter Converter Standalone client: "Unable to complete vCenter Converter agent installation on
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question https://www.experts-exchange.com/questions/26669799/VMware-Converter-4-0-x-and-Windows-2000.html Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login https://community.spiceworks.com/topic/121448-vmware-converter-4-0-x-and-windows-2000 Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > VMware Converter 4.0.x and Windows 2000 Want vmware converter to Advertise Here? Solved VMware Converter 4.0.x and Windows 2000 Posted on 2010-12-09 MS Server OS VMware Windows 2000 2 Verified Solutions 14 Comments 9,356 Views Last Modified: 2012-05-10 We need to convert Windows Server 2000 sp4 DC into vSphere. Unfortunately vSphere 4.1 with Converter 4.2 (4.3) is not supporting Windows error code 1 2000 anymore (received error code 1603). So we decided first to downloaded vCenter Converter Standalone 4.0.1 and installed it on XP machine. Agent is installed but when we try to connect the agent just stops responding. This is the output of the logs saved by the agent on the 2000 machine. Section for VMware vCenter Converter Standalone, pid=4396, version=4.0.1, build=build-161434, option=Release [2010-12-09 21:50:28.750 01980 warning 'App'] Failed to create console writer [2010-12-09 21:50:28.750 04136 info 'App'] Current working directory: C:\Program Files\VMware\VMware vCenter Converter Standalone [2010-12-09 21:50:28.750 04136 info 'Libs'] HOSTINFO: Seeing Intel CPU, numCoresPerCPU 1 numThreadsPerCore 2. [2010-12-09 21:50:28.750 04136 info 'Libs'] HOSTINFO: This machine has 2 physical CPUS, 2 total cores, and 4 logical CPUs. [2010-12-09 21:50:28.750 04136 info 'Libs'] Using system libcrypto, version 9070AF [2010-12-09 21:50:29.921 04136 info 'App'] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000 [2010-12-09 21:50:29.937 04136 info 'App'] [,0] Mntapi_Init Asked - 1.0 Served - 1.0 was succ
need to convert Windows Server 2000 sp4 DC into vSphere. Unfortunately vSphere 4.1 with Converter 4.2 (4.3) is not supporting Windows 2000 anymore (received error code 1603). So we decided first to downloaded vCenter Converter Standalone 4.0.1 and installed it on XP machine. Agent is installed but when we try to connect the agent just stops responding. This is the output of the logs saved by the agent on the 2000 machine. Section for VMware vCenter Converter Standalone, pid=4396, version=4.0.1, build=build-161434, option=Release [2010-12-09 21:50:28.750 01980 warning 'App'] Failed to create console writer [2010-12-09 21:50:28.750 04136 info 'App'] Current working directory: C:\Program Files\VMware\VMware vCenter Converter Standalone [2010-12-09 21:50:28.750 04136 info 'Libs'] HOSTINFO: Seeing Intel CPU, numCoresPerCPU 1 numThreadsPerCore 2. [2010-12-09 21:50:28.750 04136 info 'Libs'] HOSTINFO: This machine has 2 physical CPUS, 2 total cores, and 4 logical CPUs. [2010-12-09 21:50:28.750 04136 info 'Libs'] Using system libcrypto, version 9070AF [2010-12-09 21:50:29.921 04136 info 'App'] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000 [2010-12-09 21:50:29.937 04136 info 'App'] [,0] Mntapi_Init Asked - 1.0 Served - 1.0 was successful,TempDirectory: C:\WINNT\TEMP\vmware-temp\vmware-SYSTEM. [2010-12-09 21:50:29.937 04136 info 'App'] [serviceWin32,413] vmware-converter-agent service started [2010-12-09 21:51:50.937 04140 info 'App'] [serviceWin32,277] vmware-converter-agent service stopped Any idea what can be wrong? I did a quick test with clean install of 2000 sp4 and it is working great. Reply Subscribe View Best Answer RELATED TOPICS: VMWare Converter Issues no encrytion vmware converter still slow Vmware Converter & Windows 2003 Issue   7 Replies Datil OP Helpful Post Orl Dec 9, 2010 at 4:29 UTC Try using v3 of the converter 0 Serrano OP Helpful Post Peter006.5 Dec 9, 2010 at 4:31 UTC Does the 2000 system have dynamic disks or basic? Last time I tried to use the VMware converter it couldn't handle dynamic disks (about 12 months ago). I got around this by downloading a trial of Backup Exec System Recovery (BESR) and using that to make a One Time Conversion. Then I uninstalled the trial from the physical and the VM. 0 Chipotle OP Haldo98 Dec 9, 2010 at 5:21 UTC Found Conve