Web Admin UI Error

Follow
    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • Applicable SecureAuth IdP Versions: All Versions

    Description: Web Admin UI displays the following error message:

    Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [NullReferenceException: Object reference not set to an instance of an object.]
    MFC.WebApp.SecureAuth.WebAdminMaster.Populate_InstanceList() +486
    System.Web.UI.Control.LoadRecursive() +70
    System.Web.UI.Control.LoadRecursive() +189
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3177

    Possible Cause:

    The number of SecureAuth{X} application directories created in IIS does not match the number of SecureAuth{X} physical folders located in D:\SecureAuth. This can usually happen when the application directories or physical folders are deleted manually without deleting their corresponding physical folders or application directories.

    Steps/Options to Solve Issue:

    1. If the number of application directories exceed the number of physical folders, you can do any of the following options to ensure that the number of application directories match:

    a. Create the number of physical folders to match the number of application directories by copying existing physical folders, then renaming them accordingly

    b. Create the number of application directories in IIS to match the number of application

    c. Delete the number of physical folders to match the number of application directories in IIS

    d. Delete the number of application directories to match the number of physical folders in D:\SecureAuth by right-clicking on the application directory in IIS and choosing the "Remove" option.

    2. If you are creating new application directories or physical folders, you will need to perform the following for each application directory to map it to the corresponding physical folder:

    a. Right-Click on the application directory in IIS, then navigate to Manage Application -> Advanced Settings...

    b. In the Advanced Settings window, you need to set the following:

    b.1. Application Pool: ASP.NET v4.0 (IIS 7.5) / .NET 4.5 (IIS 8)

    b.2. Physical Path: D:\SecureAuth\SecureAuth{X} ({X} = integer to match the app directory number)

    b.3. Physical Path Credentials: leave blank

    b.4. Physical Path Credentials Logon: ClearText

    b.5. Preload Enabled: False

    b.6. Virtual Path: /SecureAuth{X} (should be grayed out)

    b.7. Enabled Protocols: http

    Note: The {X} in step b.2. should match the {X} in step b.6.

    c. Click OK.

    Once everything is set up, run the Reset File Perms and Shares tool to ensure that the proper permissions are set. All SecureAuth IdP VMs should come with this tool pre-installed. However, you should be able to download the latest release of the tool from this page in our documentation site:

    https://docs.secureauth.com/x/toKnAQ

    Following these steps should resolve the issue.

     

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.