ESXi Hosts and VM:s missing from vCenter inventory

[MB74]

I'm using Lansweeper v. 11.1.6.0, scanning a vSphere 8 environment. I have done all the steps in -->
Troubleshoot vCenter scanning issues - Lansweeper Community
However the Hosts and guests are not showing up in the vCenter inventory, only the Datacenter and the Datastores are visible.
What am I doing wrong? If I use the Lansweeper Devicetester I can see everything listed from the vCenter - it is just not showing up in the Web Interface

//Mathias

[Mister_Nobody]

And create support case

https://www.lansweeper.com/contact-support/

[MB74]

Thanks, I will try to do that, however since the license was purchased from a different email I can't register a support case and I get no response from sales:
"We are unable to match the email address you are currently logged in with a customer account in our systems. Please make sure that you are logged in with your business email address or contact our sales team via this link. "

[Mister_Nobody]

Try to request trial on new business e-mail and create case

[Mister_Nobody]

Run tool "c:\Program Files (x86)\Lansweeper\Service\Lansweeper.TestTools.App.exe" 

Select vcenter

Set IP and creds

View log  named as Lansweeper.TestTools.Errorlog.txt 

[shamburg]

The tool does not produce a log file. Is there something I am missing to generate one?

[MB74]

Thanks for linking to this test tool - wasn't aware of that. However, throws error when testing vCenter:
Error occurred
---------------------------
Self referencing loop detected for property 'Task' with type 'System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1+AsyncStateMachineBox`1[Lansweeper.Service.Domain.vCenter.VCenter,Lansweeper.Service.SA.Vmware.VCenterClient+]'. Path 'StateMachine.'

[Mister_Nobody]

Try new version 

https://www.lansweeper.com/product/changelog

[MB74]

Thanks, I tried upgrading to the latest version. Still the same issue unfortunately.
I have registered a support case now

[MB74]

From support -->
"The error has already been reported to our Development Team, and a bug report has already been created, LAN-12409.
Unfortunately, there is currently no work-around for this."