cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
BeatleUy
Engaged Sweeper II
Hi,

I noticed that for some reason the Scanning Queue is stuck with one particular computer and the server log writes the same line hour after hour: "DOMAIN\COMPUTER\1 scanning takes longer than 2 hours, repair wmi on this machine!"

Could you tell me how to repair WMI?

Is there a fix for LanSweeper to go on with the next computer in queue and not getting stuck with the same computer?

FYI. As a workaround I restarted LanSweeper services when this issue happened.

Thank you!

Best regards.
1 ACCEPTED SOLUTION
Hemoco
Lansweeper Alumni
Replied to via email as well. Lansweeper does try to abort scans that are taking too long. We are not always able to abort the thread however. We recommend that you either:
• Try repairing WMI on the problem computer again. There is not much more we can recommend besides a comprehensive WMI/system repair or a complete reinstallation of the machine.
- For Windows XP, you could try the comprehensive WMI rebuild method listed at the bottom of this page: http://windowsxp.mvps.org/repairwmi.htm
- For Windows 7, you could try sfc /scannow to perform a comprehensive system repair: http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm
• If you cannot repair WMI, exclude the problem machine from scanning. You can exclude computers in the Windows Computer Scan Exclusions section of Configuration/Scanning Setup/Scanning Methods.

View solution in original post

6 REPLIES 6
BeatleUy
Engaged Sweeper II
Thank you. I will have to exclude the machine for scanning as it is a new Windows 7 installation.

Thanks again.
Hemoco
Lansweeper Alumni
Replied to via email as well. Lansweeper does try to abort scans that are taking too long. We are not always able to abort the thread however. We recommend that you either:
• Try repairing WMI on the problem computer again. There is not much more we can recommend besides a comprehensive WMI/system repair or a complete reinstallation of the machine.
- For Windows XP, you could try the comprehensive WMI rebuild method listed at the bottom of this page: http://windowsxp.mvps.org/repairwmi.htm
- For Windows 7, you could try sfc /scannow to perform a comprehensive system repair: http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm
• If you cannot repair WMI, exclude the problem machine from scanning. You can exclude computers in the Windows Computer Scan Exclusions section of Configuration/Scanning Setup/Scanning Methods.
BeatleUy
Engaged Sweeper II
I have just sent you the information requested.

Regards.
Hemoco
Lansweeper Alumni
Hi,

Can you send the following to support@lansweeper.com:
-programs files/Lansweeper/service/errorlog.txt
-screenshot of configuration/scan queue.
-screenshot of the full scantime tab of the problem asset.
BeatleUy
Engaged Sweeper II
Hi. Thanks.

I've run the script, restarted the computer but I'm still getting "DOMAIN\COMPUTER\1 scanning takes longer than 2 hours, repair wmi on this machine!" every hour. That causes the queue to get stuck at that computer because I have defined to have only one computer thread (due to bandwidth).
I have enabled a second thread to avoid getting stuck but I think LanSweeper should realize that the thread is stuck and do something to avoid scanning that computer.

Thank you.
Hemoco
Lansweeper Alumni
Hi,

Please run the script in this article to repair your wmi: http://www.lansweeper.com/kb/47/How-to-repair-a-corrupt-WMI-installation.html.