Plesk is not accessible: 500.19 - Internal server error Module DynamicCompressionModule

Refers to:

  • Plesk for Windows
  • Plesk 11.0 for Linux

Created:

2016-11-16 12:40:34 UTC

Modified:

2017-02-16 14:32:31 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Plesk is not accessible: 500.19 - Internal server error Module DynamicCompressionModule

Symptoms

Plesk is not accessible

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid. Module DynamicCompressionModule
Notification SendResponse
Handler StaticFile
Error Code 0x8007007e
Requested URL https://localhost:8443/
Physical Path C:\\inetpub\\wwwroot
Logon Method Anonymous
Logon User Anonymous

Cause

Error Code 0x8007007e means ERROR_MOD_NOT_FOUND - The specified module could not be found.

This problem occurs because the ApplicationHost.config file references a module that is invalid or that does not exist.

Resolution

Note: All commands have to be executed as administrator

Locate the module reference or the DLL reference that is invalid and ensure that the file is exist and all required permissions are granted:

%windir%\\system32\\inetsrv\\appcmd.exe list config -section:system.webServer/httpCompression | findstr "dll"

    <scheme name="gzip" dll="%Windir%\\system32\\inetsrv\\gzip.dll" />
<scheme name="xpress" doStaticCompression="false" doDynamicCompression="true" dll="C:\\Program Files\\WSUS\\Services\\WebServices\\suscomp.dll" staticCompressionLevel="10" dynamicCompressionLevel="0" />

To resolve the problem:

Remove or disable the XPress compression scheme from the configuration using the command below:

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

If the command will not help, then:

  1. Create a IIS configuration backup.

    %windir%\\system32\\inetsrv\\appcmd.exe add backup BeforeEditBackup
    1. Stop IIS
  2. notepad.exe  %windir%\\system32\\inetsrv\\config\\ApplicationHost.config
  3. Locate the module reference or the DLL reference that is invalid, and then fix the reference or remove it.

  4. Start IIS

Have more questions? Submit a request
Please sign in to leave a comment.