This object is in archive!
License Issues When Attempting to Upgrade
We're attempting to upgrade to the latest version from 2.3.1, but the upgrade fails with an "Invalid license key!" error.
It's worth noting that this is occurring on our sandbox site, which has a different domain than our main license. I've just tried replacing the license with a new one, to ensure that it was correct and not expired. I've also cleared the cache and confirmed that the rest of the site is functioning normally.
Any ideas? Thanks!
Oh - If it helps, I meant to mention that the upgrade process is able to back up the system before it fails with the error.
Oh - If it helps, I meant to mention that the upgrade process is able to back up the system before it fails with the error.
Timothy,
Make sure you have the same domainname as entered on License page next to URL. If it's the same, download Main License key and replace it at application/configs. Then clean cache and try again.
If domains doesn't match or if you have developer license or developer domain it won't go through with Auto-Upgrade, so the only option will be Manual Upgrade
Let us know if you have it not working correctly on main domain.
Timothy,
Make sure you have the same domainname as entered on License page next to URL. If it's the same, download Main License key and replace it at application/configs. Then clean cache and try again.
If domains doesn't match or if you have developer license or developer domain it won't go through with Auto-Upgrade, so the only option will be Manual Upgrade
Let us know if you have it not working correctly on main domain.
Stas,
Thanks for the quick response. So, we're running this on a different subdomain which I guess explains the issue. Would you consider allowing upgrades with a development license? We prefer to test all upgrades in a sandbox environment before publishing it to our live site, but the manual upgrade process is somewhat onerous to go though every time you release an upgrade.
Thanks!
Stas,
Thanks for the quick response. So, we're running this on a different subdomain which I guess explains the issue. Would you consider allowing upgrades with a development license? We prefer to test all upgrades in a sandbox environment before publishing it to our live site, but the manual upgrade process is somewhat onerous to go though every time you release an upgrade.
Thanks!
Timothy,
Unfortunately, we allow auto-upgrades only from live server, but this would change when 3.0 is live as we've already implemented it. There won't be frequent releases in 2.x line, as the next major update will be 3.0.
But as of now, only Manual upgrade will work for dev systems.
Timothy,
Unfortunately, we allow auto-upgrades only from live server, but this would change when 3.0 is live as we've already implemented it. There won't be frequent releases in 2.x line, as the next major update will be 3.0.
But as of now, only Manual upgrade will work for dev systems.
Ok, thanks for the update. Do you have any sense of when version 3.0 is going to be released?
In the meantime, do you think it might be possible for us to obtain another full license for our testing subdomain? There's no risk of us using this subdomain as a second UR service - It's behind a whitelist firewall and is only accessible to our team for testing purposes.
Ok, thanks for the update. Do you have any sense of when version 3.0 is going to be released?
In the meantime, do you think it might be possible for us to obtain another full license for our testing subdomain? There's no risk of us using this subdomain as a second UR service - It's behind a whitelist firewall and is only accessible to our team for testing purposes.
There is no exact date about 3.0 release. Somewhere in December 2013.
You can purchase another corporate license without problems and auto-upgrade it if you have outbound connection. Just make sure to change license url to your dev environment.
Let us know if you have any questions.
There is no exact date about 3.0 release. Somewhere in December 2013.
You can purchase another corporate license without problems and auto-upgrade it if you have outbound connection. Just make sure to change license url to your dev environment.
Let us know if you have any questions.
Replies have been locked on this page!