cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
WuGe
Champion Sweeper

Since the update to v11.1.1.3 my VMware vCenter Server is not scanned anylonger.
It also no longer shows up as an asset.

WuGe_0-1698397511607.png
Before the update all was OK. The vCenter and all scanned information was there.
We upgraded from v10.6.2.0
Scanning credentials are OK.
I have the vCenter IP with credentials as scanning target to scan it manually.
I can trigger the scan manually, the IP shows up in the scanning queue but seems not to be scanned because the vCenter server does not show up as asset and the widget stays empty.

Any ideas?

Update:
Logon with the given credentials works on the webclient/webpage of the vcenter.
LS calls the api and that logon runs into the error.

20 REPLIES 20
Mister_Nobody
Honored Sweeper

There are no changes in 11130 😤

GA
Engaged Sweeper II

confirmed...

WuGe
Champion Sweeper

After I heared not back for three weeks from the support I asked when a fix is expected to be released.
The answer looks like that a fix will not be there soon: 😠

"A later Lansweeper update was supposed to address this issue. Unfortunately, the issue seems to be more complex than anticipated. At the moment, our Development Team is still looking into this issue. We hope to fix this behavior as soon as possible.
Until now, there have been no reports regarding whether this issue is related to the version of Center and ESXi installed. We will add this information to the internal investigation. As soon as we have some feedback or they require more information, we will reach out to you again.
We apologize for the inconvenience.
Kind regards,"

WuGe
Champion Sweeper

Could it be that the issue only occours on a vCenter and ESXi that is running on Version 7?
I have another vCenter that is on Version 8 and that is strangely scanned by Lansweeper.

GA
Engaged Sweeper II

We have only V7 in place. 😭

Mister_Nobody
Honored Sweeper

 LS 11121:

Exception(s) while trying to scan Esxi: Error during ESXi scanning: Object of type 'System.String' cannot be converted to type 'Lansweeper.VCenterScanning.Vim.Model.NetIpConfigInfo'.

So scanning ESXi and vCenter is still broken in the current release 11.1.2.1!?
Seems they rushed something out.
Change log is still empty:
https://www.lansweeper.com/changelog/

But the download page has the new version:

WuGe_0-1699513742368.png

https://www.lansweeper.com/update-lansweeper/





GA
Engaged Sweeper II

Same here, seems they didn't work on this within the last release.
More than two weeks no actual scan data - unbelievable.

LS 11121:

Exception(s) while trying to scan VCenter: Error during vCenter scanning: There is an error in the XML document.