This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Lansweeper Community
- Forums
- Archive
- Multiple entries stuck in scanning queue
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2014 09:13 PM
I have some computers which seem to be stuck in the scanning queue. They actuaully appear in the queue multiple times. Apparently, they have either never been scanned or are not able to be scanned at the moment. Is there a way to get them out of the queue?
Solved! Go to Solution.
Labels:
- Labels:
-
Archive
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-26-2015 01:34 PM
FYI for everyone: the customer contacted us via email. Screenshots of Configuration/Scanning Setup/Database Scripts and the customer's error log indicated that the event log database tables were huge and locking up the Compact database. Clearing event log data resolved the issue.
If you have over 1,000 assets, it is recommended that you use SQL Server as your database server, not SQL Compact. Performance will be severely impacted if you try to host thousands of assets in a Compact database. Instructions for moving from SQL Compact to SQL Server can be found here.
If you have over 1,000 assets, it is recommended that you use SQL Server as your database server, not SQL Compact. Performance will be severely impacted if you try to host thousands of assets in a Compact database. Instructions for moving from SQL Compact to SQL Server can be found here.
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-26-2015 01:34 PM
FYI for everyone: the customer contacted us via email. Screenshots of Configuration/Scanning Setup/Database Scripts and the customer's error log indicated that the event log database tables were huge and locking up the Compact database. Clearing event log data resolved the issue.
If you have over 1,000 assets, it is recommended that you use SQL Server as your database server, not SQL Compact. Performance will be severely impacted if you try to host thousands of assets in a Compact database. Instructions for moving from SQL Compact to SQL Server can be found here.
If you have over 1,000 assets, it is recommended that you use SQL Server as your database server, not SQL Compact. Performance will be severely impacted if you try to host thousands of assets in a Compact database. Instructions for moving from SQL Compact to SQL Server can be found here.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-19-2014 08:18 PM
I tried that on one of them and still have the issue with that computer. Yesterday, I upgraded again to the newest version and still have the same problem.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-13-2014 11:41 AM
Did you try repairing WMI on the affected computers?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-12-2014 10:05 PM
I have updated to 5.2. I currently have 22 computers listed as "processing" in the scanning queue. They appear to be the same ones that were previously "stuck" in there. Other computers have entered the queue and have completed processing. Also, I have it set to use 12 threads so I'm not sure why it would be processing more than that. I clicked on the clear queue button and said yes to the confirmation then nothing happens. I suppose that could be because they are listed as "processing" and not "in queue". If that is the case, do you have any other suggestions as to how to clear them?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-10-2014 02:56 PM
If you update to 5.2, you should see a Clear Queue button under Configuration/Scanning Setup/Scanning Queue. Your problem machines may have corrupt WMI. More info on this topic can be found here: http://www.lansweeper.com/kb/47/How-to-repair-a-corrupt-WMI-installation.html
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-07-2014 05:53 PM
I've already done that. That just kicks off a scan again with the same result.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-07-2014 12:38 AM
Stop and restart the lansweeper service
New to Lansweeper?
Try Lansweeper For Free
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now
Related Content
- Multiplicity constraint violated. - Azure Scan in General Discussions
- Scan Issues in General Discussions
- Excluding AWS EC2 Assets from scans On Prem Server in General Discussions
- "Last on-premises AD Domain scan" with multiple scan servers? in General Discussions
- Not able to add new credentials to scanning credentials in General Discussions
