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.

1 ACCEPTED SOLUTION
WuGe
Champion Sweeper

Problem solved here with 11.1.4.6

View solution in original post

28 REPLIES 28
WuGe
Champion Sweeper

Problem solved here with 11.1.4.6

Man69140
Engaged Sweeper II

Sorry but not for me.

after the update it still doesn't work with 11.1.4.6

Man69140
Engaged Sweeper II

Version 11.1.4.4 does not solved the problem. same error with scan test tool :

Error Getting Value From Result 'on'

System.Threading.Tasks.Task 1 [Lansweeper.Service.Domain.vCenter.VCenter]

 

In my infra both issues with ESXi and vCenter is resolved in last build.

You have to open support case.

GA
Engaged Sweeper II

Issue seems to be fixed in this version. On a first view all looks fine again on VCenter 7 scans.

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,"