Content and Localization Verbiage Editor does not work for SecureAuth0

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

    Description:
    Content and Localization Verbiage Editor does not work for SecureAuth0


    Cause:
    Another process is locking the MFA.SecureAuth.Resource.Dll 

    Resolution:

    1. Open Services.msc

    2. Navigate to the SecureAuth Cloud Transport Service.

    3. Click Stop

    4. In the Admin Console, Save the Verbiage changes

    5. Start the SecureAuth Cloud Transport Service.

     

    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.