- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-27-2023 11:11 AM - edited ‎11-22-2023 03:54 PM
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.
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.
Solved! Go to Solution.
- Labels:
-
General Discussion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-08-2024 10:31 AM
Problem solved here with 11.1.4.6
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-22-2024 02:37 PM
@Man69140 The bug LAN-16378 is still being worked upon by our developers. It is expected to be released with the next major release if there are no showstoppers.
~~~~~~~ (〃 ̄︶ ̄)人( ̄︶ ̄〃) ~~~~~~~
Sweep that LAN, sweep it!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2024 06:33 PM
"Fix" was supposed to be released today. I upgraded to 12.1.0.1 and it still does not work.
I cannot see hosts, networks, vnics, etc. All I see is storage. My hosts show up as webservers.
waited months for this fix and it is garbage 😡

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-15-2024 06:01 PM
Still no solution even after posting a case : Last reply : "Lansweeper Support case created: 00607117
Hello,It is suspected that we are running into an error parsing the certificate, though it is not yet clear what part exactly. We have created a new bug report for this: LAN-16378. We recommend checking our changelog when a new version is released to make sure this fix is included. You can find our changelog here: https://www.lansweeper.com/changelog.aspx [lansweeper.com] Kind regards,"
I confirm the Vcenter certificate is not parsed evean after flush all certificat from Vcenter and recreate the default VMCA certicate Authority.
Could you please POST if anybody have a solution for this please ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-08-2024 10:31 AM
Problem solved here with 11.1.4.6

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-08-2024 10:44 AM
Sorry but not for me.
after the update it still doesn't work with 11.1.4.6

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-18-2023 11:47 AM
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]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-18-2023 11:49 AM
In my infra both issues with ESXi and vCenter is resolved in last build.
You have to open support case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-15-2023 04:33 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-15-2023 11:38 AM
Issue seems to be fixed in this version. On a first view all looks fine again on VCenter 7 scans.
