Answer

PROBLEM

When accessing the quarantine of GFI MailEssentials, a 500.19 Internal Server Error is generated and the page is not displayed.

ENVIRONMENT

• GFI MailEssentials
• All supported environmeny

SOLUTION

1. Check to make sure that the Virtual Directory is created and is accessible within IIS. If the SpamQuarantine (or whatever it was named) site is not listed under Default Web Sites, then make sure to go to the Quarantine settings from the GFI MailEssentials Configuration Console and create it.
2. Check in the Roles in the Server Manager, that the ASP.NET components are installed. The user will also need to have Basic and Windows Authentication installedand enabled as well. Make sure to restart IIS when you make any changes, if the issue is not resolved.
3. Check the MailEssentials\Quarantine\wwwroot folder to see if the admin account has access to it. If it does not, then the configuration console will not be able to access it either
4. Ensure the user is on the latest build to avoid any issues with past bugs that might affect access to the quarantine
5. If the server is in the DMZ, it will likely not be able to authenticate with the domain, so users will need to log in every time. Windows Authentication will not be able to function properly because of access permissions.

If this does not work, take these additional steps:

Locate C:\Windows\System32\inetsrv\config\applicationHost.config and locate this section:

<location path="Default Web Site/SpamQuarantine">
<system.webServer>
<httpErrors errorMode="Custom" allowAbsolutePathsWhenDelegated="true">
<remove statusCode="401" subStatusCode="-1" /> <error statusCode="401" subStatusCode="-1" prefixLanguageFilePath="" path="E:\Program Files (x86)\GFI\MailEssentials\Quarantine\wwwroot\401.html" /> </httpErrors> <security> <access sslFlags="None" /> <authentication> <windowsAuthentication enabled="true" /> </authentication> </security> </system.webServer> </location>

Make sure to add [Added overrideMode="Allow" ] to the <location path> tag. You will also want to modify:

<httpErrors lockAttributes="allowAbsolutePathsWhenDelegated,defaultPath">

to <httpErrors lockAttributes="defaultPath">.

CAUSE

Not all ASP components are installed which makes the server not able to interpret ASP pages and their authentication levels. For the second solution, the issue is that the lock permissions within IIS are preventing our web.config from being read properly.