I have the same issue with memory consumption maxing out, which leads to service crash.
Last night it also caused BSOD on one of the scan servers (2019).
Last event from Lansweeper Error log before crashing:
2022-05-31 18:05:55,802 [XX\XXXXXXXX05\1_PS] INFO AssetName:XXXXXXXX05 AssetUnique:XX\XXXXXXXX05\1 AssetID:5227 IP:10.xx.56.xx ScanMethod:PerformanceCounters Description:AssetId: 5227 Error during performance counters scan Invalid class
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at Lansweeper.Service.SA.PerformanceCountersAgent..MoveNext()
at System.Collections.Generic.List`1.InsertRange(Int32 index, IEnumerable`1 collection)
at Lansweeper.Service.SA.PerformanceCountersAgent.Scan(ManagementScope managementScope, PerformanceMetrics metricsToScan)
at #=zWEniKQwVNjAFBUM8IZRvTF7Kd6Sn.#=zZYegc5tX1cekQ1p2Rg==(ScanningAsset #=zByhDE9X89vk5, IDbConnection #=zi$P3NkEorBRU)
2 events from Win event log captured:
7009 Error Microsoft-Windows-Service Control Manager System 31/05/2022 6:14:11 PM
A timeout was reached (30000 milliseconds) while waiting for the Lansweeper Server service to connect.
1001 Error BugCheck System 31/05/2022 6:18:33 PM
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef (0xffffab0cb71020c0, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 38785ebb-172c-4cb1-854e-acce6e7fa9e0.
It would be really good if new scan features were thoroughly tested before the release.
We run 10 scan servers across number of countries and additional admin overhead due to the bugs became a full time job...
Yes - I have raised this with Support - just to get the logs/config files (about 2GB) from all servers, compress and upload to the ticket takes half a day. And after couple of days I was advised to "delete an asset" or "restart service"...
Surely this can be done better...
