Overview

You keep getting alerts in the GFI LanGuard console that the 'Communication server is not running.'

While this error is displayed, you may encounter other issues with deployments failing to download patches or agent communications.

Solution

The 'Communication server is not running ' error usually indicates that the Communication server (Apache) on the LanGuard server machine is down.

Normally, there should be 2httpd.exe processes running on the LanGuard server machine. If you can see them in Windows Task Manager, there might be other missing requirements or environmental variables disrupting the communications. Ensure that all the Services Prerequisites, Settings, and Administrator Privileges Requirements are in place, and restart GFI LanGuard Attendant Service, that should resolve the issue.

If no httpd processes are running, this can be caused by the configuration issues or corruptuion. Proceed with the steps below.

Ensuring that the required DLL module is installed

The x86 (32-bit) versions of Visual C++ Redistributable packages for 2013, 2015, 2017, 2019, and 2022 are required to be present on any relay agent and the LanGuard server itself. Setup files are provided by Microsoft here.

Ensuring the correct configuration

The issue can be caused by using a mapped drive for the Patch Repository folder. The httpd processes need to access the Patch Repository, and if GFI LanGuard Attendant Service account used to start these processes 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.

1. Restart the GFI LanGuard Attendant Service and check for the two httpd.exe processes. If they are still not present, continue.
2. Ensure that the file toolcfg_patchautodownload.mdb is present in the C:\ProgramData\GFI\LanGuard 12\ directory.
3. In the GFI LanGuard console go to Configuration > Patch Auto-Download.
4. In the navigation pane, under Common Tasks click on Edit patch auto-download options.
5. In the Patch Auto-download Properties dialog click on the Patch Repository tab.
6. 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.

Fixing the corrupted installation

Restart GFI LanGuard Attendant Service. If the httpd processes are still not running, this can be due to a corruption of LanGuard. Try repairing your LanGuard installation. If the issue persists even after this, you have to reinstall the LanGuard server completely:

1. To keep the current configurations, export them.
2. Write down your license and database details.
3. Uninstall LanGuard via the Windows Control Panel and restart the server.
4. Check whether the GFI LanGuard XX Attendant service was removed successfully. If it is still there, remove it manually via the Registry and restart the server.
5. Disable antivirus and install LanGuard, strictly ensuring all the requirements and following the installation steps, including unblocking the installer.
6. If you exported the configurations, import them.

Testing

Restart GFI LanGuard Attendant Service. If the issue persists, contact GFI LanGuard Support.