Gray options for vCenter Host - RetrievePropertiesEx host fa

[bvin]

When attempting to convert an Azure VM to on-prem vCenter after I type in the vCenter IP, username/password it shows gray options for the Host. If I type in the credentials for an ESXi host everything works great, just not to our vCenter 7.0.3.00300. I have confirmed I am using the correct Administrator account for vCenter and even if I use administrator@vsphere.local as I can see the account is logged in from vCenter monitor and its coming from the IP of the client machine running StarWind converter. Any idea what might not allow it to work with vCenter? Here is what I show from the V2V log:

4/28 10:46:41.009 2dc Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVMSettingsESX
4/28 10:46:41.574 2dc Facility ???ERROR: getErrorFromSOAP: soap_sprint_fault - SOAP 1.1 fault "":ServerFaultCode [no subcode]
""
Detail:
4/28 10:46:41.574 2dc Facility ???ERROR: WrapperESXI::getArrayMorHost: RetrievePropertiesEx host fail - 12
4/28 10:46:41.574 2dc Facility ???ERROR: WrapperESXI::getHostInfo: getArrayMorHost is fail - 12
4/28 10:46:41.574 2dc Facility ???ERROR: VMConverter::ESXIConverter::GetHostListInfo: getHostInfo fail - 12

Screenshot.jpg (27.41 KiB) Viewed 2281 times

[yaroslav (staff)]

Greetings,

Thank you for your email. When typing destination, we are using ESXi IPs.

[bvin]

Hi y yaroslav, yes, I typed in the ESXi IP and it works and when I tried vCenter I used its IP and it failed with the error messages above. According to your release notes it says you support vCenter 6.7 and that you were testing vCenter 7.0 so is vCenter 7.0 supported or do I need to go directly to the host? Thank You

[bvin]

Also, we have tried the migration twice and once it got to 65% and this time 3% so what would this error mean? Is there anyway to pay for support for this product or is it free only?
4/29 9:25:10.004 fa4 Facility ???INFO: CPPConverting::ConvertImage: CreateOutputImage: 0
4/29 9:52:07.120 fa4 Facility ???INFO: Error: Internet Error Code - 12031
4/29 9:52:07.121 fa4 Facility ???ERROR: AzureDisk::Read: InternetReadFile is fail - 12031. The connection with the server was reset
4/29 9:52:07.121 fa4 Facility ???ERROR: AzureDisk::Read: InetError - 0, Error -
4/29 9:52:07.121 fa4 Facility ???ERROR: CPPConverting::ConvertImage: Read 3
4/29 11:43:27.198 fa4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0
4/29 11:43:27.199 fa4 Facility ???ERROR: WrapperESXI::restoreDisk: IsValidResponse morVM config false
4/29 11:43:27.199 fa4 Facility ???ERROR: VMConverter::ESXIConverter::RestoreVirtualDisk: restoreDisk fail - -1
4/29 11:43:27.199 fa4 Facility ???ERROR: ESXIDisk::Delete: RestoreVirtualDisk error - Response is incorrect.
4/29 11:43:27.445 fa4 Facility ???ERROR: CPPConverting::Convert: FAILED

Screenshot2.jpg (47.42 KiB) Viewed 2255 times

[yaroslav (staff)]

Greetings,

Please convert the VM/disk while referring to the host.

[bvin]

What do you mean exactly? Are you saying to use the ESXi host instead of trying to use vCenter? If so, that is what I tried the last two times and the migration says timed out. What does it mean timed out, is that a problem with the communication of the transfer from Azure to ESXi and I should keep trying again? Do the error messages below help determine what might have been the cause? Thank You
4/29 9:25:10.004 fa4 Facility ???INFO: CPPConverting::ConvertImage: CreateOutputImage: 0
4/29 9:52:07.120 fa4 Facility ???INFO: Error: Internet Error Code - 12031
4/29 9:52:07.121 fa4 Facility ???ERROR: AzureDisk::Read: InternetReadFile is fail - 12031. The connection with the server was reset
4/29 9:52:07.121 fa4 Facility ???ERROR: AzureDisk::Read: InetError - 0, Error -
4/29 9:52:07.121 fa4 Facility ???ERROR: CPPConverting::ConvertImage: Read 3
4/29 11:43:27.198 fa4 Facility ???WARNING: WrapperESXI::IsValidResponse: object id - 0

[yaroslav (staff)]

Thank you for your update. It seems there is a connection problem.
Please check this workaround. Please copy the file to a Windows machine, and convert it as a local file.

[bvin]

Yes, by download the VHD using Azure Storage Explorer then opening the local VHD file it converted fine directly to the ESXi host. We will use that as our workaround for now. Thank You

[yaroslav (staff)]

Thanks for your update and for sharing your experience.