Hi
It look as network issue. Take a look at vmware kb about "Found dangling SSL error: [0] error:00000001:lib(0):func(0):reason(1)" - Physical to virtual (P2V) conversion fails with the error: A general system error occurred. Found da...
What if you use the converter to export the machine to a OVF file on your local PC from Hyper-V?
Then just use the vSphere Client to import the OVF onto you ESXi host (select File and then Deploy OVF template from the menubar).
Why do you not just convert the machine as if it was a physical machine. just forget about the fact that it is running on Hyper-V and pretend it is running on Phyiscal hardware.
Well, the virtual machine is off because it is in a Hyper-V that the processor does not support virtualization, so I can not connect the virtual machine. This physical machine I installed Hyper-V is the only one I got here to the lab, I thought it would work out to a lab for V2V Hyper-V to VMware, because next week I'll need to do this in a production environment in a client company.
So, the VM is off this machine physical Hyper-V, is in the domain, DNS OK, AD is also OK, ESXi on the network and working OK, I can access the Hyper-V SCVMMfor short, the network part is everything funcioando, but do not understand why this error appears SSL
What version of Converter are you using?
further I am going to move this post to the dedicated VMware Converter forum,