vCenter - No items are listed

[LHBL2003]

I have a vCenter:
Produkt: VMware vCenter Server
Version: 8.0.3.00900 (Previously tried with 8.0.3.00400)
Build-Nummer: 25413364

Regardless of whether I specify vCenter as the source or destination in V2V, no objects from vCenter are displayed.

2026-07-21_09h15_58.png (11.21 KiB) Viewed 302 times

On the same computer where V2V is installed, I can query all hosts, VMs, and datastores via the PowerShell CLI.
https://vcenter.MyDomain.local is also possible. There are no certificate error messages either.

Code: Select all

Install-Module VMware.PowerCLI
Connect-VIServer vcenter.domain.local
Get-VMHost
Get-VM
Get-Datastore

I found this error in the V2V log. Unfortunately, I can't find any comparisons online.

Code: Select all

7/21 8:40:36.861 5070 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
7/21 8:40:36.861 5070 Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.1.848
7/21 8:40:36.861 5070 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
7/21 8:40:36.861 5070 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
7/21 8:40:36.877 5070 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 26200
7/21 8:40:36.877 5070 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - 48d0000
7/21 8:40:36.877 5070 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - 48d0000
7/21 8:40:41.699 5070 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eESXConnection
7/21 8:41:05.489 3ab0 Facility ???INFO: WrapperESXI::connect: m_url - https://vcenter.MyDomain.local/sdk
7/21 8:41:05.521 3ab0 Facility ???INFO: WrapperESXI::connect: fullName - Administrator vsphere.local, key - 52810799-0696-d163-6784-123456789123
7/21 8:41:05.521 22a8 Facility ???INFO: VMConverter::ESXIConverter::Connection::<lambda_4eab79f5f0516eba86b7810fe0d8b684>::operator (): Worker thread started.
7/21 8:41:05.521 3ab0 Facility ???INFO: VMConverter::ESXIConverter::Connection: No_timeout ESX connection
7/21 8:41:05.521 5070 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eInputVM
7/21 8:41:05.663 5070 Facility ???ERROR: getErrorFromSOAP: soap_sprint_fault - SOAP 1.1 fault "":ServerFaultCode [no subcode]
""
Detail: 
7/21 8:41:05.663 5070 Facility ???ERROR: WrapperESXI::getArrayMorHost: RetrievePropertiesEx host fail - 12
7/21 8:41:05.663 5070 Facility ???ERROR: WrapperESXI::getVMList: getArrayMorHost is fail - 12
7/21 8:41:05.663 5070 Facility ???ERROR: VMConverter::ESXIConverter::GetVMListInfo: getVMList fail - 12

SOAP SDK paths are also supported.
https://<vCenter-IP-or-FQDN>/sdk/vimService.wsdl

2026-07-21_09h37_10.png (51.43 KiB) Viewed 298 times

I log in to vCenter using administrator(AT)vsphere.local. So it's probably not a permissions issue.
The V2V machine is on the same subnet and in the same domain.
There are several data centers in vCenter, some with clusters and some without.
It doesn't work with DNS, FQDN, or IP.
I can query VMs from a ESXI-Host using root.
I can't get anything through vCenter.

Thank you very much for any ideas.

[yaroslav (staff)]

Welcome to StarWind Forum. I've forwarded your request to the dev team.
The most realistic workaround for now seems to be running the conversion through ESXi while we are looking for a solution.
Sorry for any inconvenience.

[LHBL2003]

Unfortunately, I can only implement my plan through vCenter. So I'd appreciate it if there were a solution. It might be helpful to know that the SOAP authentication request is also received by vCenter.

2026-07-21_10h47_52.png (62.94 KiB) Viewed 286 times

[yaroslav (staff)]

Thanks for your update. I've forwarded this request to the dev team.

[LHBL2003]

I would have liked to give feedback much earlier, but your website's anti-spam rule keeps telling me I have to wait a few minutes.

The images and the log are included in the attachment. Unfortunately, there are significant limitations here.
(

V2V_Diagnose_Attachments.7z

(125.41 KiB) Downloaded 4 times

)

I was able to narrow down the problem. V2V does not support folders between the DataCenter and the ESXi-host. However, I need these as a permission level. So V2V would need to support folders in the host view.
I therefore request that the V2V software be updated.

Here's my approach:

I've anonymized the content a bit. I found a log file:
Attachment: V2V_Diagnose_Attachments.7z --> vpxd.log

less /var/log/vmware/vpxd/vpxd.log
And I noticed something with SHIFT-G (for end), SHIFT-F (for follow mode), and CTRL+C (for STOP).

Error Found: There is a property error named “Host”: 2026-07-21T09:10:03.450Z

I checked the supported SOAP versions:
https://vcenter.MyDomain.local/sdk/vimS ... rsions.xml
Attachment: V2V_Diagnose_Attachments.7z --> vimServiceVersion.png

Ich habe die im Protokoll erwähnte Gruppen-ID nachgeschlagen: group-h17016.
https://vcenter.MyDomain.local.local/mo ... oup-h17016
Attachment: V2V_Diagnose_Attachments.7z --> group-h17016.png

As well as the parent group, which is a folder:
https://vcenter.MyDomain.local.local/mo ... oup-h17013
Attachment: V2V_Diagnose_Attachments.7z --> group-h17013.png

Error source identified:
- If I remove the host from the folder and move it to the DataCenter level, the error persists.
- If I delete the empty folder in the DataCenter, the error disappears.
- I then get the error with the next host in the folder of the next DataCenter.

Now all I need is a fix for the V2V software:
Support for folders in the Host view.

HostView.png (40.4 KiB) Viewed 267 times

[LHBL2003]

It really is because of the folders. I would therefore like to request a product improvement. I removed the folders, and then StarWind V2V scanned the data set.

2026-07-21_15h19_31.png (28.84 KiB) Viewed 265 times

[yaroslav (staff)]

Thanks for sharing!

[LHBL2003]

I hope, though, that this will be forwarded to the development department. Because this is a bug, not a solution.

[yaroslav (staff)]

Yup, they were given this exact thread (you are welcome to leave some kind words for them here )
Anyway, thanks for pointing out this limitation.