Overview

The GFI LanGuard console displays the message:

Communication server not running 

While this error is displayed, one notices that deployments fail to download patches and there are issues with agent communications.

Environment

• GFI LanGuard 11 and later versions/builds.
• All supported environments.

Root Cause

GFI LanGuard Attendant Service starts the httpd.exe processes. These processes need to access the Patch Repository. If the account used for these processes (GFI LanGuard Attendant Service account) does not have the mapped drive in its profile, the processes will fail to initialize. Even if the option is disabled, the Apache server will try and check the path. To this end, it is best not to use a mapped drive for these directories.

Resolution

1. Check Windows Task Manager for the presence of two httpd.exe processes. If they are not there, continue.
2. Restart the GFI LanGuard Attendant Service and check for the two httpd.exe processes. If they are still not present, continue.
3. Check to ensure that the file toolcfg_patchautodownload.mdb is present in the C:\ProgramData\GFI\LanGuard 12\ directory (or C:\Documents and Settings\All Users\Application Data\GFI\LanGuard 12\ directory on a 2003 class computer).
4. In the GFI LanGuard console go to Configuration > Patch Auto-Download.
5. In the navigation pane, under Common Tasks click on Edit patch auto-download options.
6. In the Patch Auto-download Properties dialog click on the Patch Repository tab.
7. Make sure that the Download directory and the WSUS Content folder (if specified) use either a local drive path or a UNC path (if on a remote machine).

DO NOT use a mapped drive. Also, make sure a mapped drive is not showing in the box (even if the option to Use files downloaded by WSUS is disabled). If it is showing, change it to a local drive and then disable the setting.