- The activation code (license key or activation ID) is already applied to another Nessus instance (same key used twice).
- The activation was previously applied to the same system but the local activation database is corrupted or missing, causing Nessus to attempt re-activation.
- Licensing state on Tenable's licensing servers shows the key allocated to a different host or never released after a previous transfer.
- You used an offline activation file generated for a different activation ID or different product edition (e.g., Professional vs. Manager/Scanner mismatch).
- Clock skew or mismatched product version causing validation failures interpreting the license state incorrectly.
To resolve the issue, try the following steps: