This is the most common error. It occurs when the Response.key you are trying to use was generated from a different Request.key than the one currently on the machine.
Cause: You generated a request on PC-A, went to the portal, generated a response, but then accidentally tried to activate it on PC-B. Or, you deleted the original Request.key and EDIUS created a new one before you loaded the response. edius response.key
Solution: Start over. Uninstall EDIUS, delete all .key files from the installation directory (usually C:\Program Files\Grass Valley\EDIUS [Version]\), reinstall, and generate a fresh Request.key. This is the most common error
Some aggressive antivirus software quarantines .key files because they contain cryptographic data. Add the EDIUS installation folder to your antivirus exclusions list before generating or loading any Response.key. Or, you deleted the original Request
Modern editors often ask, "Why can't I just type a key like in the old days?" The answer is piracy control and hardware locking. Grass Valley uses this system to prevent a single license from being installed on hundreds of computers.
Before upgrading a motherboard, CPU, or boot drive, manually deactivate EDIUS. In EDIUS, go to Help > License Management > Deactivate. This frees up a seat on Grass Valley’s server. Perform the hardware upgrade, then re-activate with a new Request.key. This prevents you from losing a license seat permanently.