Scan server unavailable after upgrade to 11.1.0.13

[Eximeno]

Hello,

We've upgraded our Lansweeper to 11.1.0.13 but Scan server shows always "Unavailable". We've restart LS Server service several times but Scan server status persists.

We don't see any errors on errorlog

2023-10-24 16:39:13,884 [10] INFO Started vtools v11.1.1.3 by NT AUTHORITY\SYSTEM, Port 9524, 12 Threads, 25 IP Threads, 1 Scanning Servers, Installation Mode: Dual, Time: UTC+2
2023-10-24 16:39:13,928 [10] INFO Operating System: Microsoft Windows Server 2019 Standard (OS language: Spanish (Spain, International Sort), OS version: 10.0.17763), Service Pack version: 0
2023-10-24 16:39:13,985 [10] INFO .NET Framework version: 6,0,1623,17311 @Commit: 1e620a42e71ca8c7efb033fd525f04be5fa701fe
2023-10-24 16:39:13,993 [10] INFO Database: SQL Server 2014 (version: 12.0.6433.1) Express Edition (64-bit): (localdb)\.\LSInstance, 835.6 MB used, time: UTC+2
2023-10-24 16:39:13,999 [10] INFO License: Ultimate version, 394751017, 1194 licensed assets
2023-10-24 16:39:36,535 [4] INFO Started cleanup for uni tables.
2023-10-24 16:39:37,151 [4] INFO Uni table cleanup finished.

Nor in the web_errorlog.txt

Can you help us?

Thanks in advance, Santi.

[Mister_Nobody]

11.1.6.0, LsPush 8.4.100.1, LsAgent Windows 10.4.2.0, SQL 910 31/01/2024
Fixed: LAN-15943 In rare cases, the scan server went down.
Fixed: LAN-15962 The RMADUSER cleanup option incorrectly removed users that were present and enabled in Active Directory from the Lansweeper data.
Fixed: LAN-16067 The scanning server could randomly go down, and the scanning service could stop working.

[Mister_Nobody]

Problem is still present.

The LS-process runs for 10 minutes and stops.

[Mister_Nobody]

https://community.lansweeper.com/t5/general-discussions/new-lansweeper-release-version-11-1-4-3/td-p...

[Coffee-scanner]

I face the same issue here. The scan server is unavailable, and I contacted support.
They cannot give me any other solution for now so I am stuck and cannot scan the assets in our network.

[Mister_Nobody]

Has anyone verified this error in LS 11130?

[StillGoing]

We ran into this same issue. Lansweeper support has confirmed that there is a known bug and it has been passed on to development. But they have provided no details, and there is no ETA on when the issue will be addressed.

We are running into additional issues since, including deployment issues. Our logs are full of errors, and it is obvious that there are scans that are not completing properly, even though the asset is shown as being successfully scanned. CPU utilization on all our scanners is higher than normal, but at least the servers eventually stabilized and are not hanging any more.

I should have known better than to jump on an update so soon after release.

[StillGoing]

Our servers have stabilized, but it has become obvious that some data is not getting updated during scheduled scans (manual scans seem to work better). There are also issues with deployments which they have also confirmed as a bug.

Basically, it's either roll back or wait for them to fix it. In their words:

We have examined the log files and found the issue is a known issue, and it has been escalated to our development team as a bug. A fix for it will be in a future release. Unfortunately, there is no estimated release date, however, we are hopeful that the patch next week will resolve the issue. We recommend checking our changelog when a new version is released to ensure this fix is included (LAN-15873). You can enable the update check in the Lansweeper web console under Configuration\Your Lansweeper License to be notified of any new releases.

You can find our changelog here: https://www.lansweeper.com/changelog.aspx

We apologize for the inconvenience and appreciate your patience while the fix is being created.

[Mister_Nobody]

I don't see LAN-15873

but LS writes all changes very rarely

[StillGoing]

Yeah, I noticed that. And the deployment bug we confirmed (LAN-15899) isn't listed either. 

We have already rolled back to the previous version, and I don't think I'll be jumping on any v11 releases until someone can confirm the issues have been dealt with.