- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago - last edited 4 weeks ago
We have some Windows-assets with endless WMI-scanning.
So we have two porblems:
1. LS doesn't have working timeout but we see log record (Aborted mydomain\rds-sql\1 scanning takes longer than 1 hour, wmi might need a repair on this machine.)
2. And then we have duplicates of assets in scanning queue.
As result scanning queue full and LS doesn't have slot for new scanning.
"Clear queue" button also not works for such assets.
Solved! Go to Solution.
- Labels:
-
Scanning
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@Mister_Nobody
indeed check is the WMI needs repairing on the Windows asset that is blocking the queue.
https://community.lansweeper.com/t5/troubleshooting-scanning-issues/repair-a-corrupt-wmi-installatio...
Restarting the scanning server should free up the memory and scanning queue. Not ideal but works as a last resort.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@Mister_Nobody
indeed check is the WMI needs repairing on the Windows asset that is blocking the queue.
https://community.lansweeper.com/t5/troubleshooting-scanning-issues/repair-a-corrupt-wmi-installatio...
Restarting the scanning server should free up the memory and scanning queue. Not ideal but works as a last resort.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Now I restart LS service every night...
