Troubleshooting: Object Reference Error on the Workflow or Post Authentication Tab

Follow
    Applies to:
  • SecureAuth Identity Platform
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected: All
     
     

    Overview

    Navigating to either the Workflow tab or the Post Authentication tab returns an "Object reference not set to an instance of an object" error instead of loading the page.

    ASP.NET Server Error page for the SecureAuth0 application, showing a System.NullReferenceException with a stack trace referencing MFC.WebApp.SecureAuth.WebAdminWorkflow.ReadWebConfig and ReadRealmSettings.

     

    Cause

    This is caused by an issue with one of: the realm's web.config, the MFC.WebApp.SecureAuth.dll file present in the SecureAuth0 application, or the page file for the affected tab (WebAdminWorkflow.aspx for the Workflow tab, or WebAdminComplete.aspx for the Post Authentication tab).

     

    Resolution

    Try the following in order until the page loads successfully:

    1. Run an Update Web.config on the realm, to restore any settings that may be missing from the web.config.
    2. If that does not resolve it, back up the existing MFC.WebApp.SecureAuth.dll file in D:\Secureauth\SecureAuth0\bin, replace it with a copy of the same file from the Template folder, then perform an IIS reset and try the Workflow or Post Authentication page again.
    3. If that still does not resolve it, back up the affected page file — WebAdminWorkflow.aspx for the Workflow tab, or WebAdminComplete.aspx for the Post Authentication tab — and replace it with a copy from the Template folder.

     

    Special Considerations

    Before replacing the DLL, you may need to stop the Cloud Transport service temporarily, since that service can hold a lock on the DLL and prevent it from being replaced.
     
     

    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.