You have an issue with an Agent scheduled daily scans, or those initiated by right-clicking on Agents to refresh information, not starting. At the same time, the manual console scans are working correctly.
The described behavior may be caused by permission issues or indicate that certain configuration files have become corrupted.
- If you are not using the latest LanGuard version, Upgrade LanGuard first, and verify whether the issue is gone.
- Verify the permissions and possible environmental issues following the solution steps of the Why is the Activity Monitor Not Showing Scheduled Scans and Remediation Results? article.
It is possible that the database is almost full; in this case, you should free up some space in the database. See Maintaining and improving the performance of the SQL Database Used by LanGuard.
If certain Agents are still not scanning, it is possible that the Agent installation is corrupted; uninstall the GFI LanGuard Agent on the target machine and reboot it. Once the uninstallation completes, restart the GFI Attendant service on the LanGuard server, then redeploy the GFI LanGuard Agent.
If the issue persists, certain configuration files may be corrupted. In such cases, it is recommended to reinstall the LanGuard server, strictly ensuring all the requirements, disabling antivirus, and following the installation steps.
Some Agents can be stuck on the old build number after this. If this happens, try to Manually Update LanGuard and right-click on Agents to refresh information and force an update. If the build still doesn't update, please uninstall the agent, wait for it to uninstall, and redeploy it again from the console.
Perform an agent scan from the LanGuard console by right-clicking on the target machine in the network tree and selecting Scan > Refresh information now. If the issue persists, contact GFI LanGuard Support.