After every few months due to Chrome updates we have to update TestComplete. Having a node lock license its a pain. I end up spending hours for each upgrade running into new issues every time no matter how carefully done.The process I use for new release:
Uninstall TC (if version change instead o patch, e.g. 10.6 -> 12.1)
Upgrade new version
Some of the problems I run into:
- License does not deactivate -
- Have to do offline deactivation,
- then offline deactivation does not work,
- then when it does complete finally, it does not deactivate on my licence page.
- Sentinel (the license manager) with TestComplete does uninstall correctly, restart the VM and do the whole process again
- Then sometime we run into problems with regenerating licenses
- Then it does not activate, have to do offline activation sometimes.
We have 5 VMs and I start getting nightmares when I have to upgrade.
You don't need to deactivate the license to upgrade TestComplete.
You even can upgrade it over the old version.
Or I misunderstood something?
Well, as per the general process we should not have to, but for some reason I have ran into problems when the license was not deactivated first.
For instance, if the installation process gets jacked up somehow (which it does very easily since last two upgrades), you would have to deactivate the existing license first, which then becomes a huge problem. So I found it better off to deactivate it already Just In Case.
So after doing the last upgrade, here are the steps when I followed did not run into a roadblock:
Again, this is not the way suggested by SmartBear's support, but by hit and trial this is what I have found to cause less problems.
So you've contacted Support about this or are you just working from the support pages?
I would bug Support directly until you get a better resolution than this. I've never had to go through that many steps to upgrade.
I did contact support, they helped out with the 'deactivation started' problem where the license would not deactivate, but did not mention a different flow for upgrading.
I've done these updates around 10 times since we have been using TestComplete (since v10.3), and each time there is a new problem I come across. The key here is if during upgrade the install hits a problem whih it usually does with the Sentinel licensing tool, that turns into a long story. I find it safer to deactivate and then upgrade. Since I have to do at least 5 VMs, eventually I do ruin into problems with at least on VM.
Another issue here I think is using a node lock on a VM, the licensing structure makes it really hard to upgrade in this configuration, for understandable reasons, but the user suffers too.
Sounds weird as personally I never had upgrade problems...
> Another issue here I think is using a node lock on a VM
Might it be the reason of your problems? Node-locked license is not recommended to be used on VMs: https://support.smartbear.com/testcomplete/docs/licensing/license-types.html (Node-Locked License section).