Overview

Some of the computers you have the agent installed on do not scan according to the schedule set up.

Solution

As the scheduled scans are not starting for only a few of the computers, this usually indicates that some of the environmental requirements are not met for these computers, potential database issues, or the corruption of the LanGuard agents or server.

1. Restart the LanGuard Server and run a new Scheduled Scan on the same machine (or group of machines) where the previous Scheduled Scan attempts failed.

2. Check the free space on the server hosting the database and the current database size and fix any found issues there Maintaining the SQL Database Used by LanGuard article.  If there is enough space but the database or log files reached the limit, Increase the size of a database or add data or log files to a database.
3. There might be names resolving and network connectivity problems with the affected computers - Verify Required Network Connectivity and Security Permissions for GFI LanGuard Operations.
4. Antivirus software or Firewall interference can lead to unexpected LanGuard behavior; verify and configure proper exclusions, both on the server and target machines.
5. Restart the GFI LanGuard Attendant service and later on check whether scans started at a designated time. If scheduled scans are still not starting for some machines, Uninstall LanGuard Agent on the target machine(s) and make a fresh Agent Deployment.
6. If the problem is still there, this would indicate a corrupted LanGuard server installation. Please, proceed to repair the installation.

Testing

Check whether scans now start according to the schedule. If the issue persists, contact GFI LanGuard Support.