p2v of windows 2019 server failing with Unexpected Exception: vmodl.fault.SystemError

[NASAWest]

Team IHAC who is trying to p2v conversation of a windows 2019 server and failing with the following:

"The target datastore is an NFS mount on the ESXi server"

2022-10-18T15:38:09.650-04:00 error vmware-converter-server[14660] [Originator@6876 sub=Default] [task,350] [LRO] Unexpected Exception: vmodl.fault.SystemError

2022-10-18T15:38:09.650-04:00 info vmware-converter-server[14660] [Originator@6876 sub=Default] [task,379] [task-2] -- ERROR -- Convert: vmodl.fault.SystemError

--> (vmodl.fault.SystemError) {

--> faultCause = (vmodl.MethodFault) null,

--> reason = "Server closed connection after 0 response bytes read; <io_obj p:0x05fe9aa8, h:2192, <pipe '\\.\pipe\vmware-converter-worker-soap'>, <pipe '\\.\pipe\vmware-converter-worker-soap'>>",

--> msg = ""

--> }

any ideas how to get around this?

[Preeti-P]

Hi,

Can you please check - the source VM is accessible from server? and Firewall is off.

Thanks,

Preeti

[NASAWest]

Hello Pretty, 

checking with customer if the source windows 2019 server vm is accessible and if the firewall is turned off. 

[NASAWest]

Hello Preeti, so we opened port 443 and 902 and tried again, and we get  failure...the vm is created, but not data is written to the destination. 

doesn't look like I can upload an image of the error here, but I have an screen shot of the error we are seeing. 

[ivivanov]

"\\.\pipe\vmware-converter-worker-soap" indicates this is the communication between the Server and Worker services. "Closed connection" means the other end of the named pipe was closed, which can happen when Worker service exited - either on service stop (manually, or e. g. by windows update manager), or more likely - if the service crashed. Can you please check in Services Control UI if the Worker service is still running, if there are any events related to the VMware vCenter Converter Worker service in the Windows Event log (e. g. crash, restart) and also look in the worker log for some more detailed errors, and specifically - for a backtrace (it should be along with the server log).