Overview

You may notice that Scheduled Scans are not running or starting as required. This may include Scheduled Scans configured from the console or the agents, as well as patch deployments.

This article analyzes the root cause of this issue, along with the available solution.

Diagnosis

A scheduled scan is a network audit that is scheduled to run automatically on a specific date/time and at a specific frequency. GFI LanGuard ships with a patch auto-deployment feature that enables users to deploy missing patches and service packs in all languages supported by Microsoft® products.

GFI LanGuard installation or upgrade deploys services and modules responsible for various actions. A common root cause for the remote actions not starting or running as required is when the sub-module agentmanagercom.dll is not registered correctly in the GFI LanGuard server.

Solution

Initially, 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. If the issue persists, you may follow the steps below:

1. Log in to the GFI LanGuard server. 
2. Close the GFI LanGuard.
3. Stop all the LanGuard services.
   1. Press Windows + R keys together to open the Run dialog box.
   2. Type services.msc and press the Enter key.
   3. Locate and stop the GFI LanGuard ... services.
4. Open the Command Prompt in elevated mode:
   
   1. Click Start.
   2. Type cmd in the search box.
   3. Right-click on cmd.exe and choose Run as Administrator.
   4. In the User Account Control window, click Yes to run the Windows Command Prompt as an administrator.
5. Run the following command:
   

   regsvr32 "C:\Program Files (x86)\GFI\LanGuard xx\agentmanagercom.dll"

   NOTE: Replace xx in the above path with the version number of the GFI LanGuard.
6. Start GFI LanGuard.
7. Reopen the console.

Testing

Schedule a scan and verify whether it is starting as expected. If the issue remains, please contact our technical support team.