Scanserver Queue Cleanup

[DaveinJP]

Hung computers eventually use all configured slots in a scanserver queue eventually creating the symptom of more "in process" computers than the scanserver is configured for. Stopping/starting the service clears this most of the time where as "clear queue" does not. Stopping the service usually fails and the process must be terminated from the Task Manager and then restarted.

What can be done to improve policing of scan queues and elimination of hung scans that are causing a problem like this?

[Daniel_B · Accepted solution]

We recommend that you try repairing WMI on the computers which hang during scanning. Instructions on how to repair a corrupt WMI can be found in this KB article.

If this does not resolve the issue, could you send a mail to support@lansweeper.com with the following:

• link to this forum topic
  
• Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on your Lansweeper server.
  
• Screenshots of one problem client machine's Lansweeper webpage. Show us the following tabs: Summary, Scan Time, Errors (if it exists).
  
• Screenshot of a connection test performed to the same problem client machine with testconnection.exe, which can be found in Program Files (x86)\Lansweeper\Actions on your Lansweeper server. Perform the test from your Lansweeper server to the client machine, submit the same credential used by Lansweeper to scan the client and show us the entire test window.
  

[DaveinJP]

good to know that I'm not alone. Stopping service often leads to killing process in taskman because the service won't stop.

[intloc]

I would like to know it too, because there are some assets, that can be "in process" for weeks, and nothing helps. I tried to clear queue, restart service... nothing helps.

[DaveinJP]

are there start options for the scanserver process? Command line switches?