Hi,
Thanks, I change datastor to another and run task with thick disks and its work!
Thanks a lot!
Hi,
Thanks, I change datastor to another and run task with thick disks and its work!
Thanks a lot!
Hi,
I have the same issue and I found a solution. Not sure if this will help but I thought I'd post as this thread is coming high up in Google searches.
My fix was changing a registry key.
1. Open HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control in the Windows Registry Editor and create or modify a ServicesPipeTimeout DWORD32 decimal value to at least 300000 (5 minutes).
2. Restart the system for the changes to take effect.
Note this was done after the above steps so I'm not sure if all of the lanman service and SMB issues affected me.
C
Perfect! This works for me!
Thanks kolonuk!
FAILED: A general system error occurred: Server closed connection after 0 response bytes read; <io_obj p:0x04022c34, h:
1228, <pipe '\\.\pipe\vmware-converter-worker-soap'>, <pipe '\\.\pipe\vmware-converter-worker-soap'>>
Error above.
I am currently trying to convert Win7 PC to VM and loading it onto a External Hard Drive. How am I getting a response error? I ran as admin and am supposed to be connecting to the same device......
See attached logs for details
The most interesting log, worker's one, is missing. You can find it in "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs" folder and upload here.
What's the best way to P2V a Windows XP machine? I see the standalone converter doesn't list that as a supported guest OS. Unfortunately the software on the machine isn't available anymore so I'm trying to be as un-intrusive as possible so as not to cause any issues with the machine; just want to be able to have a working full backup of the machine in the event the hardware goes.
Try the Converter 6.2 even is not listed as supported OS because it's EOL it should works.
HTH
What about "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs"?
Hi I am trying to convert a HyperV VM to VMware, but I am getting the error:
"An error occurred during the conversion: 'converter.fault.NoHostConnection'"
fullMessage = "Unable to clone disk C:\ClusterStorage\csv01\a185\Virtual Hard Disks\a185.vhdx on the virtual machine 'a185'.",
The VM has its disk on a ClusterStorage directory.
Does anyone know how to resolve this issue?
It's always better to use the latest Converter, currently 6.2.0.1
Are you sure that wr-vcenter.tuiad.net:443 is visible from source machine? as well as ESX-name-or-ip:902?
You should check the conversion prerequisites before starting the conversions.
However seems that reported hard disk for this machine is not recognized, this is strange, except if its logical sector size is 4096 which is not supported by Converter. You'll need to check this.
HTH
You can use this one for Xp:
VMware-converter-en-6.0.0-2716716.exe
Every time I've used it (Xp is same codebase as 2003), I never got any issues.
There's also no destructive loss should a P2V fail.
You'll always have the original physical box to uninstall the converter, re-install perhaps another build, and try it yet again.
There's really no need to do a cold conversion, where you shut down the box and boot off an .iso or PE to run the P2V. First, those builds were really old. And the live converters have gotten more reliable.
I had the problem with the converter 6.2 ... there is no longer a converter-worker.xml there is only one singel file - converter-client.xml
so I entered the SSL option code, then the converter could connect... and then I tried to convert a VM and it spit into my face with a message "cant read hardware settings". wtf?
I belive it can't by design... and this has to do with some no longer supported storage configurations. With the other direction I had to hack the vmx files, then the converter 6.2 did convert my player 6.5 VMs... the root cause was a vmdk file pointing to a physical disk. But I wont touch my "golden sample" which contains 5 years of lessons, research and tests. And there are only iSCSI or local volumes...
I have to say today I lost my faith in VMware products... also because of a purple screen with an original and vmware supported Intel Quadport E1000 card in a VMware supported mainboard...
Try to find XMLs in folder "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\"
HTH
The "can't retrieve hardware information" error comes from the format of old .VMX files (< ESX 5.5 or < WS 10) aid it is not related to the SSL problem, that happens with VMX files on a regular hard drive too. I know the workarounds, but the solution is to do the convert with an older converter version.
The thread is about SSL connections and fix for TLS1.0 with XML files.
If you experience issues to connect with UI, the same issue will happens with services' connections, so you can't change only value in converter-client.xml and work successfully.
For your other problem(s) you must open new thread(s) attaching appropriate logs into.
Regards
Found it, here :
Seems that worker service crashes, are there some .dmp files in folder?
Also please check for worker's dmp files according Drwtsn32 on Windows Vista/Windows Server 2008/Windows 7/Windows Server 2008 R2 – Yong Rhee's Microsoft Technet Blog
Hopefully dump files will give us a clue what's happens.
hi,
I installed VMware vcenter converter 6.2.0 build 8466193 (latest one) which has in log history fix for smb share I had.
Conversion of a powered on Windows machine to an SMB share fails with the following error message: Unable to obtain the lock on virtual disks
.
This issue is resolved in this release.
even that issue was fixed I have another issue which is thrown once I execute convertion ... with status FAILED: Insufficient permissions to access the source.
2018-11-09T15:32:38.150+01:00 info vmware-converter-server[17732] [Originator@6876 sub=Default] [task,379] [task-2] -- ERROR -- Convert: converter.fault.ImportSourceNoPermission
--> (converter.fault.ImportSourceNoPermission) {
--> faultCause = (vmodl.MethodFault) null,
--> source = "\\10.0.1.129\storage3-shared\vmware-x11-clone-20181109\x11\x11.vmx",
--> msg = ""
--> }
why clone to SMB share is still broken? or do I miss something?
thanks
"Insufficient permission" should be self explanatory error, but probably you miss to give enough permission for share and/or, if target is NTFS, for folder's permission.
The easiest way is to add read/write permissions for everyone, otherwise you'll need to add read/write permissions for used user and for computer accessing share.
HTH