Contents x
    "Your Request Cannot Be Processed" Error
    • 05 Dec 2023
    • 1 Minute to read
    • Contributors
    • Print
    • Dark
      Light
    Contents

    "Your Request Cannot Be Processed" Error

    • Updated on 05 Dec 2023
    • 1 Minute to read
    • Contributors
    • Print
    • Dark
      Light
    Article summary

    "Your Request Cannot Be Processed" Error is a diagnosis that can mean one of many things. The following are the most known causes of the error.

    Check Your Version

    The file paths used are under the assumption that your MFA server is on 4.9.5.1 or later. If it is not, it is strongly recommended to upgrade. Please see our server upgrade information page for more information.

    SSL Certificate Is Expired

    If you utilize SSL/HTTPS with your MFA server's URL, this has proven to be one of the leading causes of the error. Check your IIS server certificate to determine if this is the case, then go through the process of renewing it with your preferred certificate authority, if applicable.

    Configuration Files Are Misconfigured

    If you do not use SSL, there could be an issue with the configuration files. This can sometimes happen when upgrading to a newer version, and the URL settings once in place have been reverted to a default value (usually back to the server's computer name). The following instructions will need to be performed in the following files:

    • C:\Program Files\Identity Automation\RapidIdentity MFA\WebSite\ web.config
    • C:\Program Files\Identity Automation\RapidIdentity MFA\ServiceSite\ web.config
    • C:\Program Files\Identity Automation\RapidIdentity MFA\RestServices\ web.config
    • C:\Program Files\Identity Automation\RapidIdentity MFA\API\ web.config
    1. In an elevated Notepad or text editor, open the files listed above.
    2. In each file, look for your MFA server's URL. If it's as it should be, there's no fix needed to that file. If you cannot find your usual URL, it might be because it's been changed back to the server's computer name.
    3. If you find an inconsistency, correct all the occurrences within the file (Ctrl+h is the 'Replace' shortcut). The files in ServiceSite and API are typically the ones that revert.

    SQL Database Update Tool Was Not Run

    When upgrading, our database update tool is required so the SQL MFA database is up to date with the changes (version, keys, records, etc.).

    1. Open an elevated command prompt.
    2. Navigate to C:\Program Files\Identity Automation\RapidIdentity MFA\tools
    3. Run the following command:
    TwoFA.CM.DBUpdate /v

    Other Quick Items To Check

    • Check that your SQL service is running on the MFA and/or AD server
    • Are all the MFA server dependencies installed?
    • If Microsoft's Web Service Enhancement 3.0 is installed, it may not have been installed correctly. Reinstall and select 'Administrator' mode during the install process.
    • Check that the 'hosts' file has a loopback for the MFA portal URL
    example: 127.0.0.1     mfa.idauto.one
    Was this article helpful?
    What's Next