ERROR configuring IIS to enable proxy

Follow
    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • SecureAuth IdP Version Affected:  9.3

     

    Description: 

    When upgrading to 9.3 the Updater displays this error:

    Begin: update system components... 
    Begin: installing IIS components... 
    Configuring IIS to enable proxy... 
    ERROR configuring IIS to enable proxy: System.Runtime.InteropServices.COMException (0x80070490): Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config 
    Error: The configuration section 'system.webServer/proxy' cannot be read because it is missing a section declaration

    at Microsoft.Web.Administration.Interop.AppHostWritableAdminManager.GetAdminSection(String bstrSectionName, String bstrSectionPath)
    at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath) 
    at SecureAuthUpdater.ApplianceManager.InstallIISComponents() 
    Restarting IIS... 
    End: installing IIS components. 
    End: update system components

     

    Cause

    IdP 9.3 requires the IIS component called Application Request Routing.

    ARR and 2 more installers are a prerequisite for the updater.

     

    Resolution

     

    Extract the SecureAuth 9.3 Updater to a folder on the D: drive and run the following installers prior to upgrading:
     
    <updater path>MFCApp_Bin\Extras\.NETCore2HostingComponents\dotnet-hosting-2.1.3-win.exe
    <updater path>MFCApp_Bin\Extras\ReverseProxyComponents\requestRouter_amd64.msi
    <updater path>MFCApp_Bin\Extras\ReverseProxyComponents\rewrite_amd64_en-US.msi

     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.