Am converting a DMZ server and am getting "a general system error occurred: unknown internal error" just as im clicking finish on the VM converter.
I have followed this KB and have opened up the ports on the firewall to the VSphere host server, do i need to open the same ports on the VMHOST server as well?
I see few problems here:
2013-05-27T15:03:40.593+01:00 [04220 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: The process cannot access the file because it is being used by another process (32)
2013-05-27T15:03:40.593+01:00 [04220 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
You can search the process that blocks access to your C:
2013-05-27T15:08:39.171+01:00 [04220 warning 'Default'] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server ***********11.ds.local failed: No such host is known
The DNS name is not visible, you can workaround using IP instead of DNS name.
I have cleaned down the worker log file so its only displaying the last attempt.
This is what i have done so far
i have removed the vmhost from vsphere so im converting directly to the host. used IP addresses instead of host names.
i have amended the firewall rules so the ports listed on the KB are open for both the DMZ server and vmhost but its still crapping out when submitting the job with the following error "a general system error occurred: unknown internal error"
Could you review the logs again,
Many many thanks
As you can see your error is
2013-05-28T13:23:55.328+01:00 [00808 warning 'Default'] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Failed to connect to server *******:902
You must check for firewalls, ipsec and any other tools that can prevent connection, also double check for ports required for connection like 902. Try to telnet your ESX at port 902 to verify.
An idea: could you remove (temporary) the machine from DMZ? The routers often disallows access from the DMZ to internal zones...
I had the same error message: unknow error.
In my case the destination server was a vcenter server. The vcenter server manages two esx servers. The converter retrieves the network-names of the esx servers from vcenter. The machine that I was trying to convert was not able to get the ip-number for the selected esx server by its name as registered with vcenter.
added ip-number and esx network name in hosts file of the machine to be converted
(windows: c:\windows\system32\drivers\etc\hosts, linux: /etc/hosts)
example host file entries (assuming your vcenter server is called 'vcenter', the registered network names of the esx servers are 'esx1' and 'esx2') and assuming the ip-numbers are 10.10.10.21, 10.10.10.22 and 10.10.10.23):
After saving the hosts file, I restarted the converter and all went well.