VMware Converter 4.0.x and Windows 2000
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 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\
[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.
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\
[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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Last one for today. Tried the 2003 machine also with Converter 4.2 from vSphere Client
"Unable to complete vCenter Converter agent installation on 'ip address'. Error code: 1,603."
Hopefully tomorrow will be better day.
"Unable to complete vCenter Converter agent installation on 'ip address'. Error code: 1,603."
Hopefully tomorrow will be better day.
Hi
Don't use dns names, use IP, for connections between converter and VMware(source and destination).
Also to prevent problems, do not connect the vConverter into a vCenter, but into a VMware host(if you are using vCenter or VMware ESX) as the destination to that VM.
Follow all the tasks and the process(use the scripts) from the article, and you will fix many of the issues.
Jail
Don't use dns names, use IP, for connections between converter and VMware(source and destination).
Also to prevent problems, do not connect the vConverter into a vCenter, but into a VMware host(if you are using vCenter or VMware ESX) as the destination to that VM.
Follow all the tasks and the process(use the scripts) from the article, and you will fix many of the issues.
Jail
ASKER
I'm use always IP addresses in operation like this.
I just managed to convert one 2003 machine with Convertor 3 and vmkfstools. So far it is running great, after re-adding of the virtual HDD and NIC. Testing further.
Convertor 4.x.x is still not working.
I just managed to convert one 2003 machine with Convertor 3 and vmkfstools. So far it is running great, after re-adding of the virtual HDD and NIC. Testing further.
Convertor 4.x.x is still not working.
ASKER
here is current progress
- not able to connect to any 2000 machine in our network
- able to convert 2003 machines with Converter 3.0.3 and vmkfstools into vSphere
- able to convert 2008 and 7 machines with Converter 4.2 plugin into vSphere
and...
- if I try to connect with Converter 3.0.3 to any other machine I get "ERROR: Failed to take snapshot of a source volume. Possible causes include not having any NTFS volumes on Windows XP or Windows 2003 source systems, and not having enough free disk space."
- if I try to connect with Converter 4.2 to any other machine I get "error code 1603"
- not able to connect to any 2000 machine in our network
- able to convert 2003 machines with Converter 3.0.3 and vmkfstools into vSphere
- able to convert 2008 and 7 machines with Converter 4.2 plugin into vSphere
and...
- if I try to connect with Converter 3.0.3 to any other machine I get "ERROR: Failed to take snapshot of a source volume. Possible causes include not having any NTFS volumes on Windows XP or Windows 2003 source systems, and not having enough free disk space."
- if I try to connect with Converter 4.2 to any other machine I get "error code 1603"
Hi
In the Windows 2000 there is the last Service Pack installed?
Can this be an Firewall issue on that servers?
Jail
In the Windows 2000 there is the last Service Pack installed?
Can this be an Firewall issue on that servers?
Jail
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi
Please can you provide the logs from the conversion.
Jail
Please can you provide the logs from the conversion.
Jail
ASKER
Logs from 2003 machines? I will upload them when I will be in office again.
Hi
When you do a convert using a vConverter the converter will create a log of the conversion and will save in the physical machine, upload that log.
In the end of that conversion you can go to file and choose to save that log.
Provide that log here please.
For Windows 2000, can you do a cold migration?
Jail
When you do a convert using a vConverter the converter will create a log of the conversion and will save in the physical machine, upload that log.
In the end of that conversion you can go to file and choose to save that log.
Provide that log here please.
For Windows 2000, can you do a cold migration?
Jail
ASKER
In last few days I tested the P2V (v4.2) with most of the 2003 and 2008 machines we have here. No more errors for now (although I don't know exact reason why).
I didn't test the cold migration as the Converter 3.0.3 is running now great.
I will reopen the question if needed. Thanks for your time.
I didn't test the cold migration as the Converter 3.0.3 is running now great.
I will reopen the question if needed. Thanks for your time.
ASKER
patch was missing on given systems
ASKER
I know about the DC's, but since this is still in test lab we don't really care about it and just wanted to test this. Mean time we did some more test. Added 2 more machines to the test - 2003 server and another 2000 server (no DC). With Converter 3.0.3 (in starter mode) the process started successfully (stopped it after 5%). Then we tried the same machines with Converter 4.0.1 -> "Unable to access the remote Converter Standalone Agent service. It either does not exist or is not responding".