Overview

Installed on Windows servers and clients LanGuard Agents keep failing to download program updates, new missing patches and vulnerabilities definitions files. The Activity Monitor and Agent management show failed state for the Agent updating jobs, and the Agent Status message in the LanGuard console Computer Tree reports health issues: "Last update failed" or "Unable to get latest update".

Solution

There are several possible root causes for the GFI LanGuard agent failing updates error; most of them are related to the environmental changes or missing requirements. Also, the updated definitions are only provided to the latest versions of the product that are released. If you are not using the latest LanGuard version, Upgrade LanGuard first, and verify whether the error is gone.

1. One of the common reasons for the Agent update failures is the LanGuard server itself not updating. In the LanGuard console Activity Monitor tab check Program Updates Activity -> GFI LanGuard Updates for the error "Failed to validate the integrity of the file." If you see this error, follow the steps from the Error: 'Failed to validate the integrity of the file' While Running the Update article.

   If you see any other errors with LanGuard server updates, Update LanGuard Server Manually and verify whether the error is gone.

2. Ensure that the required Firewall Ports are open on the target machine(s) with an Agent and on the LanGuard server. Also, the firewall might block outbound connections as well; refer to the Recommended Settings for Best Performance in GFI LanGuard for the relevant configuration guidelines.

   Once the settings are ensured to be in place, Perform all the Required Network Connectivity Tests and Verify Security Permissions. Fix all the issues you find during these checks.

3. Antivirus software can be the cause of the update operations failing, verify and configure proper exclusions.

4. In some environments, updates may fail due to low timeout settings. To address this, on the LanGuard server:
   1. Increase an HTTP timeout setting by editing/adding the following directive in the C:\Program Files (x86)\GFI\LanGuard 12 Agent\Httpd\conf\httpd.conf:
      

      Timeout 600

   2. Increase the connection timeout.
   3. Restart the GFI LanGuard XX Attendant service.

Testing

Trigger Agent scan by right-clicking on the target machine in the network tree and selecting Scan > Refresh information now. The Agent will automatically run an update before the scan. Verify the Agent status after the scan finishes.

If the issue persists, Uninstall LanGuard Agent on the target machine and make a fresh Agent Deployment.

Related Articles

• Updating LanGuard Server Manually When Product Does Not Get Latest Definitions or Agents Do Not Update 
• Required Settings to Scan a Machine and Successfully Install Missing Patches Using GFI LanGuard 
• Verifying Required Network Connectivity and Security Permissions for GFI LanGuard Operations