Scanning took longer than 30 minutes

[AdmJLovejoy]

I'm seeing several Scan Aborts on many servers. Is there a config that I've missed to adjust scan time timeouts?

[Hemoco]

This is changed in the latest version of the beta, please test and confirm.

[AdmJLovejoy]

Any update?

[Hemoco]

AdmJLovejoy wrote:
Any update?

This will be changed in the next update.

[AdmJLovejoy]

Again, I have to rule out any WMI issues or this would be apparent in other backend support systems. It appears 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.

Many of the servers that are showing this error, have many nested AD Groups and Groups from External Forests. Lansweeper is terminating the scan prior to completion.

[Hemoco]

I think it's better to find the cause of the long scan times.
WMI usually times out after 5 minutes.

[AdmJLovejoy]

Is possible to get this bumped up to 60 mins?

[AdmJLovejoy]

Yes, this does allow me to validate my suspicions that scans are being aborted before a full scan has been completed. Looks like "Usersingroup" and "Desktop" are the heavy hitters. This brings me back to my original question, now that we know scans are not completing before the default 30 min threshold is reached. Is there any way to extend the scan time beyond the default 30 min threshold?

[Hemoco]

AdmJLovejoy wrote:
Yes, this does allow me to validate my suspicions that scans are being aborted before a full scan has been completed. Looks like "Usersingroup" and "Desktop" are the heavy hitters. This brings me back to my original question, now that we know scans are not completing before the default 30 min threshold is reached. Is there any way to extend the scan time beyond the default 30 min threshold?

It's currently hardcoded (was also the same in previous versions)

[Hemoco]

Can you click the wait times open on the action page to look at the scan time of each item.