MIDAS Knowledge Base MIDAS Knowledge Base

Why is my MIDAS ID blocked?

As part of the validation process whenever you install or update a self-hosted MIDAS system, the validity of your unique MIDAS ID (product key) is checked.

If this validation process fails, you'll receive the following an on-screen notification and will be unable to proceed further with the install/update:

The Authorization Server detected that the MIDAS ID you entered appears to have been used on multiple servers, and so has blocked it.

Validation of your MIDAS ID may fail for a number of reasons, including:

  1. You have attempted to install more instances of MIDAS than your MIDAS ID (product key) allows. (Typically, our self-hosted license permits you to install one live instance and one separate test instance only)
  2. You've moved your MIDAS system to a different server/URL, and haven't used our online Self Service Maintenance tool to let us know of the change.
  3. Your MIDAS ID (product key) has become public, and therefore we have pro-actively withdrawn it to prevent abuse.

To resolve an "Authorization Failed" message, please ensure that you have not installed more instances of the software than your MIDAS ID allows (typically two, as per the license).

If you are "moving" your existing MIDAS system over to a new server with a different domain name, please follow the instructions in our "How to relocate MIDAS to a new server" KB article.

If you are "re-installing" a MIDAS system, please ensure that you install to the same location (URL) as your existing system. (Please note that your-domain.com and www.your-domain.com will be viewed as two different locations by the installer)

If your domain name has changed since you last installed MIDAS, please use our online self service maintenance tool to update your MIDAS configuration.

If you've followed the above steps and are still unsure when your MIDAS has been blocked, then please contact us and we'd be happy to advise and assist.

You might also be interested in...

MIDAS » KB » Support » Article 00184

← Return to the Knowledge Base