
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-02-2025 10:19 PM
Lansweeper scan service use out all memory, over 10GB. Any idea how to trouble shoot the issue?
- Labels:
-
General Discussion
-
Question
-
Scanning
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-05-2025 09:17 PM
If you open a case, we can analyze your logs and database table and provide some recommendations. The most common culprits are Windows event log scanning and sometimes debug mode.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-05-2025 09:21 PM
Already opened a case and sent out the logs.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-03-2025 05:21 AM
Same here. I upgrade to version 12.4.1.2 all my Lansweeper server and notice most of them are having high CPU util. I tried restarting services but after quite some time it will go back to High Util. We only experience this after 12.4.1.x version.
Are there any version update to be release soon?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-02-2025 11:47 PM
Check Scanning Queue Size & Frequency
Too many scan tasks queued and running simultaneously can lead to excessive memory use or database load.
- High-frequency scan schedules (e.g. every 5 mins)
- Repeating schedules with overlapping scans
- Very broad IP ranges
Check Performance scanning is enabled if so try disabling to see if that helps. It's possible there are performance scanning targets hogging up the queue since these run in the background and are not visible on the scanning queue
Are you scanning more than just errors with the event scanning.
SQL Database Performance (if on-prem)
A bloated or underperforming database can trigger memory spikes on the scan server indirectly.
Run database cleanup tool : C:\Program Files (x86)\Lansweeper\Tools
- Stale assets
- History size
- tblNtlog, tblSoftware, tblEventlog

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-02-2025 11:02 PM
We recently experienced high CPU on our Lansweeper server, we tried stopping/restarting the Lansweeper Service first which fixed it for a while, when it started happening again we stopped/restarted the service again and now it's been at normal usage.
If the above doesn't work for you, I would open a case with Lansweeper support.
