Phone Lines icon GFI Support Home

Articles in this section

See more

HTTP error 500.19 with code 0x8007007e when synchronizing with Central Management Server

Author: Andriy Rybalchenko Updated

Overview

After installing Central Management Server (CMS) the synchronization fails and the GFI LanGuard console shows the error:

Error encountered while synchronizing: Error status 'ProtocolError', message 'the remote server returned an error: (500) Internal server error.'

Also, when opening the Web console the following error is displayed:

HTTP error 500.19 with the error code 0x8007007e

Another web page, usually WSUS, is also hosted on the IIS and propagates incorrect settings to other web sites.

Prerequisites

An account with Administrator Privileges.

Diagnosis

Error 0x8007007e translates as ERROR_MOD_NOT_FOUND - The specified module could not be found.

CMS runs using Microsoft IIS and this problem usually occurs when WSUS (or web page with similar behavior) is hosted on the IIS. The XPress compression scheme module (suscomp.dll) gets installed with WSUS and the schemas are defined globally. They try to load in every Application Pool, regardless of whether it is 64-bit or 32-bit. Such behavior results in an error when 64-bit version of suscomp.dll attempts to load in an Application Pool which is running in 32-bit mode.

To verify the issue:

  1. Go to C:\Windows\System32\inetsrv\config\.
  2. Open the file applicationHost.config with a text editor.
  3. Find the entry:

<scheme name="xpress" doStaticCompression="false" doDynamicCompression="true" dll="C:\Windows\system32\inetsrv\suscomp.dll" staticCompressionLevel="10" dynamicCompressionLevel="0" />

Solution

Remove/Disable the XPress compression scheme from the configuration following these steps:

  1. Open a command prompt running as administrator.
  2. Run the following command:

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

  1. Type IISreset and press Enter.

More information can be found at https://blogs.msdn.microsoft.com/webtopics/2010/03/08/troubleshooting-http-500-19-errors-in-iis-7

Testing

Once the IIS configuration is fixed and Application Pool restarted, perform the steps below:

  1. Restart the GFI LanGuard Services.
  2. Open the Web console.
  3. Open the Languard console and force the sync by running a scan on the server itself.

Related articles