Deep Scan Stuck with no Scan Process


Run a scan on a Discovery Network, Deep Scan will get stuck with no "percentage complete" status and no error code. When you check the @MsgQueOut folder in the working directory you can see the XML files generated.


Possible Cause

 While Deep Scan can get stuck for a number of variables, one of the possible reason is that the working directory has been placed inside of the WINDOWS folder. This path is forbidden and Kaseya is not able to monitor and pull the Lan Watch XML files from that location.

xmls.jpg (1061×659)


Under Agent --> Manage Agents --> Working Directory, change the working directory for your agents from the C:\WINDOWS\Kworking path to C:\Kworking. Once the Directory has been changed run a new Discovery Scan. 

working1.jpg (406×667)


Have more questions?

Contact us

Was this article helpful?
0 out of 9 found this helpful

Provide feedback for the Documentation team!

Browse this section