I'm assuming you downloaded the latest version of converter? What OS is mailserver1? Did you try running converter from the server?
↧
Re: Errors trying to covert VM?
↧
Re: Errors trying to covert VM?
Hi,
Can you check with the block size of the destination datastore might be does not support a VMDK as large as the source.
OR
When you try to convert a VM with Paravirtual SCSI Controller, VMware Converter throws you a nice error and the task fails with Status: FAILED: An error occurred during the conversion
Try doing this:
– Change all Paravirtual controllers to LSI Logic (VM MUST be powered off)
– Do NOT poweron the VM from now on
– Perform the Convert, make sure VM is not powered on automatically after convert
– Change SCSI controller back to Paravirtual
– Power on VM
To change a SCSI controller, open Edit Settings… from the VM and select the SCSI Controller. Click the Change Type… button and modify the SCSI Controller Type.
↧
↧
Re: Errors trying to covert VM?
I'm running Converter 6 locally on a Windows 8 machine. Destination is not to a datastore but to the local Win8 NTFS filesystem. I see theres a converter 6.1 which I'm trying now. When I try to convert the source VM is a powered off Linux VM. I'll report back soon, thanks for the help.
↧
Re: Errors trying to covert VM?
I updated Vmware Convert to 6.1.1. Exact same problem. Log highlights say "Error: Unable to clone disk [MyDataStoreName]". Source VM is only 4.6GB in size. So thats not the problem. SCSI Controller Type is BusLogic which has been fine for like 10 years. All of a sudden I have this problem, which has surfaced right after I installed Veeam Backup & Replication.
When I try to Convert a local Vmware workstation machine on the Win8 machine up to the ESX server it also fails but with a different error:
FAILED: An error occurred during the conversion:
'The operation experienced a network error'
Always right at the end at 99% done.
↧
Re: Errors trying to covert VM?
How much free space should a datastore have to do snapshots? I have a backup job with Veeam that is working and it says in the logs as it works "Creating snapshot". The VM size is 14GB and the free space on the datastore is 28GB. Sounds ok.
I have another VM that fails on the same datastore but the size of that VM is 130GB, do I need more free space to make it work then?
↧
↧
Re: Errors trying to covert VM?
These are the GUI logs.
Click in the failed task and select "export logs"
↧
Re: Errors trying to covert VM?
It is possible that Veeam interferes with the conversion. If you can stop it and retry, it's worth trying.
Since the error is at 99%, the cloning has passed. You can try just configure the destination VM if it it Windows and power it on.
If all that fails - post the worker's log.
↧
Re: Unable to convert volume mounted on /boot
I have the exact same issue. Ever find out what was going on?
↧
Re: Errors trying to covert VM?
Its a linux destination guest. I put logs here that probably have the working stuff in it if anyone can take a look:
http://sites.extremehosting.ca/temp/ConverterDiagnostics20161101191643.zip
↧
↧
Re: Error : Permission to perform this operation was denied -- Log : Must be administrator to access physical computer
Yes, this was EXACTLY the cure to my issue, too! Thanks for posting.
↧
Converter failing with: The operation experienced a network error
I can't believe there is any kind of network issue because all of my VM's are working and on the network.
I am running version 6.1.1 and have tried three different ESXi servers. Two are 5.5 and one is 6.0 servers and they all fail. I have also tried this on another PC that fails.
I have also tried different VM's to import. I took one of the VM's and converted it on my PC from one drive to another drive and that works telling me the VM isn't the issue.
I found one article on the web from VMware Converter: "The operation experienced a network error" - discussing the network error issue but said it was something else that he got around.
The other strange thing it does, the progress bar gets to 50% and then speeds up to 98% and then goes back to 6% where it fails.
I have attached the log files from one of the tests.
Thanks
↧
Re: Converter failing with: The operation experienced a network error
Not sure, but I experienced "network issues" in the past, and they were related to DNS resolution, where the target ESXi host's name couldn't be resolved. Adding an entry to the hosts file solved the issue.
If this doesn't help in your case, check the entries of the converter's "worker" log file, to see whether this contains more detailed information about the issue.
André
↧
Re: Converter failing with: The operation experienced a network error
Thanks for the reply. I don't believe that is my issue because I used the IP address to connect to the vCenter Server on two of the host servers and the other server that's on v6 of ESXi I used it's host name which was resolved thru DNS.
↧
↧
Re: Converter failing with: The operation experienced a network error
Please upload the whole log bundle to check what has happened. The GUI log is the least informative one.
Thanks
↧
Re: Converter failing with: The operation experienced a network error
Attached is the log you requested.
Thanks
↧
Re: Converter failing with: The operation experienced a network error
Here is the error
2016-11-07T09:45:33.296-05:00 warning vmware-converter-worker[06188] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1
2016-11-07T09:45:33.296-05:00 warning vmware-converter-worker[06188] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcFile_SendMessage: hdr send failed:
2016-11-07T09:45:33.296-05:00 warning vmware-converter-worker[06188] [Originator@6876 sub=Default] [,0] [NFC ERROR] The operation experienced a network error -- Failed to send header message
2016-11-07T09:45:33.296-05:00 info vmware-converter-worker[07256] [Originator@6876 sub=task-5] Worker CloneTask updates, state: 1, percentage: 5, xfer rate (Bps): 63605760
2016-11-07T09:45:33.296-05:00 info vmware-converter-worker[07256] [Originator@6876 sub=task-5] Worker CloneTask updates, state: 1, percentage: 5, xfer rate (Bps): 3168256
2016-11-07T09:45:33.296-05:00 warning vmware-converter-worker[06188] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcSendFile: Failed to send block track file 'C:\Users\Phil.CORP\Desktop\Windows 7 VM\Windows 7 VM-ctk.vmdk': 3
2016-11-07T09:45:33.296-05:00 error vmware-converter-worker[06188] [Originator@6876 sub=task-6] Sysimgbase_Nfc_PutFile failed in H2MDiskCloneMgr with nfcError 'The operation experienced a network error' (error code:3)
NFC stands for network file control, it is a proprietary file transfer protocol used by Converter. Unfortunately its code base is outside the Converter's one and I can't suggest what exactly this error means.
As an attempt for workaround - in case the source files have a rather poor network connection with the destination ESX, could you try copying them somewhere else and retry the conversion?
Regards,
Plamen
↧
Re: Converter failing with: The operation experienced a network error
I tried three different conversions. I install the converter on a Dell 2012 server and tried it and failed. I then installed the converter on a Windows VM that is on my ESXi-01 server. I then copied the VM to import and tried the import to my ESXi-05 server and it failed. I then tried it again going to the ESXi-01 server. This would eliminate the network because all of the network traffic is going thru the ESXi virtual network adapter and virtual switch on the same server. I am attaching the logs for that.
↧
↧
Re: Converter failing with: The operation experienced a network error
I just did another test and this time I took a Linux server VM that was on ESXi-01 and converted it to my PC desktop. I then took the VM that I just put on my PC and went back to ESXi-01 and created another VM and this worked. I am attaching the logs in case you want to look at something.
The VM that keeps failing is a Windows 7 VM but as I stated before I took the VM and run it thru the converter and created another copy on my PC to prove the VM was OK.
↧
Re: FAILED: Unable to create a VSS snapshot of the source volume(s).
Three years on and this saved our bacon. How the hell you found this I will never know but its awesome.
Glad you updated your own post.
↧
Re: Converter failing with: The operation experienced a network error
It is the same error in the log as before,
I'll ask the people from NFC team in case they can suggest anything.
Regards,
Plamen
↧