‎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.
‎01-08-2024 10:31 AM
Problem solved here with 11.1.4.6
‎10-31-2023 01:32 PM - edited ‎10-31-2023 01:34 PM
Lansweeper support confirmed there is a known issue with vcenter and esxi scanning and they are working on it.
They will release a fixed version soon.
LS support recommended to check the changelog page for updates.
https://www.lansweeper.com/changelog/
‎10-30-2023 09:25 AM - edited ‎10-30-2023 09:25 AM
Please scan vCenter via
"c:\Program Files (x86)\Lansweeper\Service\Lansweeper.TestTools.App.exe"
‎10-30-2023 09:31 AM
Thanks.
That tool immediately throws an error when trying to scan the vcenter:
‎10-30-2023 09:20 AM - edited ‎10-30-2023 09:20 AM
I opened a support case now.
‎10-30-2023 08:55 AM - edited ‎10-30-2023 08:56 AM
When I start a manual scan of my vCenter Server my windows eventlog is filling with errors related to that job:
The first error in detail:
And I also have hundreds of .net errors that are lsagent related:
‎10-30-2023 04:28 AM
Also Some Esxi-host are not scanning in my infrastructure
Vmware Error Unknown error
‎10-30-2023 08:48 AM
@Mister_Nobody So it seems to be here too.
I do have them as asset but all the information / details are missing.
‎10-27-2023 06:23 PM - edited ‎10-27-2023 06:26 PM
Are you sure the Scan Service isn't crashing and failing to scan it at all?
I'm in the process of trying to figure out why our Scan Server constantly crashes after upgrading to 11 (I do have a ticket open, and they're looking into it). But from what I've found so far, mine crashes when I scan something by IP. but I'm still trying to trace it down. Not sure if its exactly due to it being by IP, or if its just non-windows items. As our Windows PC's & Servers pulled from AD seem to scan just fine. But Printers/Linux devices lock up the scan server service.
‎10-30-2023 08:45 AM - edited ‎10-30-2023 08:49 AM
@AlbertD222 What do you mean in datail? My scaning service is up&running.
Your scanning service crashes and is stopped?
Or do you mean windows eventlog entries?
‎10-30-2023 04:23 PM
Sorry just seeing this. Looks like you opened a ticket, but still wanted to answer your question...
Our Scan Server freezes I guess is the best way to put it. The Service is "Running" on the server, but in Lansweeper it says its stopped. If I stop the service in Windows it eventually times out with an error, and then lets me start the service back up. Which then works for a while until I either scan an item based on its IP or Linux based item (not sure which causes the problem, yet). If i turn all scanning off, and only leave Active Directory scanning on, it works fine.
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now