This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Scanning took longer than 30 minutes

AdmJLovejoy
Champion Sweeper

‎12-25-2010 09:43 PM

I'm seeing several Scan Aborts on many servers. Is there a config that I've missed to adjust scan time timeouts?
Thanks, Jim Lovejoy __________________________________________________________________________________________________ James W. Lovejoy | IBM - Cloud Managed Services Delivery | Infrastructure Architect (Windows Server ...
Labels:
Preview file
37 KB
0 Kudos
11 REPLIES 11
AdmJLovejoy
Champion Sweeper

‎12-31-2010 05:37 PM

I have to rule out any WMI issues or this would be apparent in other backend support systems. I'm guessing that the time it takes to pull a large number of users/groups, and/or a large number of event logs exceeds the default 30 min threshold.

Either way, scans are not completing before the 30 min threshold is reached. Is there any way to adjust this?
Thanks, Jim Lovejoy __________________________________________________________________________________________________ James W. Lovejoy | IBM - Cloud Managed Services Delivery | Infrastructure Architect (Windows Server ...
0 Kudos
Hemoco
Lansweeper Alumni

‎12-31-2010 01:37 PM

Version 4.0 had the same behaviour, but there the error was written to errorlog.txt

This usually happens with a corrupt WMI installation which lock the WMI process.
0 Kudos

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now